View MBM29DL64DF-70_4569128.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

ds05-20905-1e fujitsu semiconductor data sheet flash memory cmos 64 m (8 m 8/4 m 16) bit dual operation mbm29dl64df -70 n description mbm29dl64df is a 64 m-bit, 3.0 v-only flash memory organized as 8 mbytes of 8 bits each or 4 m words of 16 bits each. the device comes in 48-pin tsop (1) and 48-ball fbga packages. this device is designed to be programmed in system with 3.0 v v cc supply. 12.0 v v pp and 5.0 v v cc are not required for write or erase operations. the device can also be reprogrammed in standard eprom programmers. the device is organized into four physical banks : bank a, bank b, bank c and bank d, which are considered to be four separate memory arrays operations. this device is the almost identical to fujitsus standard 3 v only flash memories, with the additional capability of allowing a normal non-delayed read access from a non-busy bank of the array while an embedded write (either a program or an erase) operation is simultaneously taking place on the other bank. (continued) n product line up n packages part no. MBM29DL64DF-70 power supply voltage v cc (v) 3.0 v max address access time (ns) 70 max ce access time (ns) 70 max oe access time (ns) 30 + 0.6 v - 0.3 v 48-pin plastic tsop (1) 48-ball plastic fbga (fpt-48p-m19) (bga-48p-m13) marking side
mbm29dl64df -70 2 (continued) the new design concept called flexbank tm * 1 architecture is implemented. with this concept the device can execute simultaneous operation between bank 1, a bank chosen from among the four banks, and bank 2, a bank consisting of the three remaining banks. this means that any bank can be chosen as bank 1. (refer to n functional description for simultaneous operation.) the standard device offers access times 70 ns, allowing operation of high-speed microprocessors without the wait. to eliminate bus contention the device has separate chip enable (ce ) , write enable (we ) and output enable (oe ) controls. this device supports pin and command set compatible with jedec standard e 2 proms. commands are written to the command register using standard microprocessor write timings. register contents serve as input to an internal state-machine which controls the erase and programming circuitry. write cycles also internally latch addresses and data needed for the programming and erase operations. reading data out of the device is similar to reading from 5.0 v and 12.0 v flash or eprom devices. the device is programmed by executing the program command sequence. this invokes the embedded program algorithm tm which is an internal algorithm that automatically times the program pulse widths and verifies proper cell margin. typically each sector can be programmed and verified in about 0.5 seconds. erase is accomplished by executing the erase command sequence. this invokes the embedded erase algorithm tm which is an internal algorithm that automatically preprograms the array if it is not already programmed before executing the erase operation. during erase, the device automatically times the erase pulse widths and verifies the proper cell margin. each sector is typically erased and verified in 0.5 second (if already completely preprogrammed) . the device also features sector erase architecture. the sector mode allows each sector to be erased and reprogrammed without affecting other sectors. the device is erased when shipped from the factory. the device features single 3.0 v power supply operation for both read and write functions. internally generated and regulated voltages are provided for the program and erase operations. a low v cc detector automatically inhibits write operations on the loss of power. the end of program or erase is detected by data polling of dq 7 , by the toggle bit feature on dq 6 , or the ry/by output pin. once the end of a program or erase cycle is completed, the device internally returns to the read mode. the device also has a hardware reset pin. when this pin is driven low, execution of any embedded program algorithm or embedded erase algorithm is terminated. the internal state machine is then reset to the read mode. the reset pin may be tied to the system reset circuitry. therefore if a system reset occurs during the embedded program tm * 2 algorithm or embedded erase tm * 2 algorithm, the device is automatically reset to the read mode and have erroneous data stored in the address locations being programmed or erased. these locations need rewriting after the reset. resetting the device enables the systems microprocessor to read the boot-up firmware from the flash memory. fujitsu flash technology combines years of flash memory manufacturing experience to produce the highest levels of quality, reliability, and cost effectiveness. the device memory electrically erases the entire chip or all bits within a sector simultaneously via fowler-nordhiem tunneling. the bytes/words are programmed one byte/ word at a time using the eprom programming mechanism of hot electron injection. *1 : flexbank tm is a trademark of fujitsu limited. *2 : embedded erase tm and embedded program tm are trademarks of advanced micro devices, inc.
mbm29dl64df -70 3 n features ? 0.17 m m m m m process technology ? two-bank architecture for simultaneous read/program and read/erase ? flexbank tm * 1 bank a : 8 mbit (8 kb 8 and 64 kb 15) bank b : 24 mbit (64 kb 48) bank c : 24 mbit (64 kb 48) bank d : 8 mbit (8 kb 8 and 64 kb 15) two virtual banks are chosen from the combination of four physical banks (refer to n functional description flexbank tm architectureand example of virtual banks combination.) host system can program or erase in one bank, and then read immediately and simultaneously from the other bank with zero latency between read and write operations. read-while-erase read-while-program ? single 3.0 v read, program, and erase minimized system level power requirements ? compatible with jedec-standard commands uses the same software commands as e 2 proms ? compatible with jedec-standard worldwide pinouts 48-pin tsop (1) (package suffix : tn - normal bend type) 48-ball fbga (package suffix : pbt) ? minimum 100,000 program/erase cycles ? high performance 70 ns maximum access time ? sector erase architecture sixteen 4 kword and one hundred twenty-six 32 kword sectors in word mode sixteen 8 kbyte and one hundred twenty-six 64 kbyte sectors in byte mode any combination of sectors can be concurrently erased. also supports full chip erase. ? hiddenrom region 256 byte of hiddenrom, accessible through a new hiddenrom enable command sequence factory serialized and protected to provide a secure electronic serial number (esn) ? wp /acc input pin at v il allows protection of outermost 2 8 kbytes on both ends of boot sectors, regardless of sector group protection/unprotection status at v acc , increases program performance ? embedded erase tm * 2 algorithms automatically preprograms and erases the chip or any sector ? embedded program tm * 2 algorithms automatically programs and verifies data at specified address *1 : flexbank tm is a trademark of fujitsu limited *2 : embedded erase tm and embedded program tm are trademarks of advanced micro devices, inc. (continued)
mbm29dl64df -70 4 (continued) ? data polling and toggle bit feature for program detection or erase cycle completion ? ready/busy output (ry/by ) hardware method for detection of program or erase cycle completion ? automatic sleep mode when addresses remain stable, the device automatically switches itself to low power mode. ? low v cc write inhibit 2.5 v ? program suspend/resume suspends the program operation to allow a read in another byte ? erase suspend/resume suspends the erase operation to allow a read data and/or program in another sector within the same device ? sector group protection hardware method disables any combination of sector groups from program or erase operations ? sector group protection set function by extended sector group protection command ? fast programming function by extended command ? temporary sector group unprotection temporary sector group unprotection via the reset pin. ? in accordance with cfi (c ommon f lash memory i nterface)
mbm29dl64df -70 5 n pin assignments (continued) tsop (1) (fpt-48p-m19) a 15 a 14 a 13 a 12 a 11 a 10 a 9 a 8 a 19 a 20 we reset a 21 wp/acc ry/by a 18 a 17 a 7 a 6 a 5 a 4 a 3 a 2 a 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 normal bend a 16 byte v ss dq 15 /a -1 dq 7 dq 14 dq 6 dq 13 dq 5 dq 12 dq 4 v cc dq 11 dq 3 dq 10 dq 2 dq 9 dq 1 dq 8 dq 0 oe v ss ce a 0 (marking side)
mbm29dl64df -70 6 (continued) n pin descriptions pin function a 21 to a 0 , a -1 address input dq 15 to dq 0 data input/output ce chip enable oe output enable we write enable reset hardware reset pin/temporary sector group unprotection ry/by ready/busy output byte selects 8-bit or 16-bit mode wp /acc hardware write protection/program acceleration v cc device power supply v ss device ground n.c. no internal connection fbga (top view) (marking side) (bga-48p-m13) a6 b6 c6 d6 e6 f6 g6 h6 a 13 a 12 a 14 a 15 a 16 byte dq 15 / a -1 v ss a5 b5 c5 d5 e5 f5 g5 h5 a 9 a 8 a 10 a 11 dq 7 dq 14 dq 13 dq 6 a4 b4 c4 d4 e4 f4 g4 h4 we reset a 21 a 19 dq 5 dq 12 v cc dq 4 a3 b3 c3 d3 e3 f3 g3 h3 ry/by wp/ acc a 18 a 20 dq 2 dq 10 dq 11 dq 3 a2 b2 c2 d2 e2 f2 g2 h2 a 7 a 17 a 6 a 5 dq 0 dq 8 dq 9 dq 1 a1 b1 c1 d1 e1 f1 g1 h1 a 3 a 4 a 2 a 1 a 0 ce oe v ss
mbm29dl64df -70 7 n block diagram n logic symbol v cc v ss a 21 to a 0 (a -1 ) reset we ce oe byte wp/acc dq 15 to dq 0 dq 15 to dq 0 bank a address bank c address bank b address bank d address state control & command register status ry/by control cell matrix 8 mbit (bank a) x-decoder y-gating cell matrix 8 mbit (bank d) x-decoder y-gating cell matrix 24 mbit (bank b) x-decoder y-gating cell matrix 24 mbit (bank c) x-decoder y-gating 22 a 21 to a 0 we oe ce dq 15 to dq 0 16 or 8 byte reset a -1 ry/by
mbm29dl64df -70 8 n device bus operation mbm29dl64df user bus operations table (byte = = = = v ih ) legend : l = v il , h = v ih , x = v il or v ih , = pulse input. see n dc characteristics for voltage levels. *1 : manufacturer and device codes are accessed via a command register write sequence. see command definitions table. *2 : refer to sector group protection in n functional description. *3 : we can be v il if oe is v il , oe at v ih initiates the write operations. *4 : v cc = 2.7 v to 3.6 v *5 : also used for the extended sector group protection. *6 : protects outermost 2 4 kwords on both ends of the boot block sectors (sa0, sa1, sa140, sa141) . operation ce oe we a 0 a 1 a 2 a 3 a 6 a 9 dq 15 to dq 0 reset wp / acc standby h x x x x x x x x high-z h x autoselect manufacturer code * 1 llhlllllv id code h x autoselect device code * 1 llhhllllv id code h x extended autoselect device code * 1 llhlhhhlv id code h x llhhhhhlv id code h x read * 3 llha 0 a 1 a 2 a 3 a 6 a 9 d out hx output disable l h h x x x x x x high-z h x write (program/erase) l h l a 0 a 1 a 2 a 3 a 6 a 9 d in hx enable sector group protection * 2, * 4 lv id lhlllv id xhx verify sector group protection * 2, * 4 llhlhlllv id code h x temporary sector group unprotection * 5 xxxxxxxxx x v id x reset (hardware) /standby x x x x x x x x x high-z l x boot block sector write protection * 6 xxxxxxxxx x x l
mbm29dl64df -70 9 mbm29dl64df user bus operations table (byte = = = = v il ) legend : l = v il , h = v ih , x = v il or v ih , = pulse input. see n dc characteristics for voltage levels. *1 : manufacturer and device codes are accessed via command register write sequence. see command definitions table. *2 : refer to sector group protection in n functional description. *3 : we can be v il if oe is v il , oe at v ih initiates the write operations. *4 : v cc = 2.7 v to 3.6 v *5 : also used for extended sector group protection. *6 : protect outermost 2 8k bytes on both ends of the boot block sectors (sa0, sa1, sa140, sa141) . operation ce oe we dq 15 / a -1 a 0 a 1 a 2 a 3 a 6 a 9 dq 7 to dq 0 reset wp / acc standby h x x x x x xxxx high-z h x autoselect manufacturer code * 1 llh l lllllv id code h x autoselect device code * 1 llh l hllllv id code h x extended autoselect device code * 1 llh l lhhhlv id code h x l lh l hhhhlv id code h x read * 3 llha -1 a 0 a 1 a 2 a 3 a 6 a 9 d out hx output disable lhh x xxxxxx high-z h x write (program/erase) l h l a -1 a 0 a 1 a 2 a 3 a 6 a 9 d in hx enable sector group protection * 2, * 4 lv id l lhlllv id xhx verify sector group protection * 2, * 4 llh l lhlllv id code h x temporary sector group unprotection * 5 xxx x xxxxxx x v id x reset (hardware) / standby xxx x xxxxxx high-z l x boot block sector write protection * 6 xxx x xxxxxx x x l
mbm29dl64df -70 10 mbm29dl64df command definitions table * 1 (continued) command sequence bus write cycles reqd first bus write cycle second bus write cycle third bus write cycle fourth bus read/write cycle fifth bus write cycle sixth bus write cycle addr. data addr. data addr. data addr. data addr. data addr. data read/ reset * 2 word 1xxxhf0h ?????????? byte read/ reset* 2 word 3 555h aah 2aah 55h 555h f0h ra* 12 * 12 rd ???? byte aaah 555h aaah autoselect word 3 555h aah 2aah 55h (ba) 555h 90h ia* 12 id* 12 ???? byte aaah 555h (ba) aaah program word 4 555h aah 2aah 55h 555h a0h pa pd ???? byte aaah 555h aaah program suspend 1bab0h ?????????? program resume 1 ba 30h ?????????? chip erase word 6 555h aah 2aah 55h 555h 80h 555h aah 2aah 55h 555h 10h byte aaah 555h aaah aaah 555h aaah sector erase word 6 555h aah 2aah 55h 555h 80h 555h aah 2aah 55h sa 30h byte aaah 555h aaah aaah 555h erase suspend* 3 1bab0h ?????????? erase resume* 3 1ba30h ?????????? set to fast mode word 3 555h aah 2aah 55h 555h 20h ?????? byte aaah 555h aaah fast program * 4 word 2 xxxh a0h pa pd ???????? byte reset from fast mode * 5 word 2 ba 90h xxxh * 11 00h ???????? byte extended sector group protection * 6, * 7 word 3 xxxh 60h spa 60h spa 40h * 12 spa * 12 sd ???? byte query * 8 word 1 (ba) 55h 98h ?????????? byte (ba) aah hidden- rom entry* 9 word 3 555h aah 2aah 55h 555h 88h ?????? byte aaah 555h aaah
mbm29dl64df -70 11 (continued) *1 : command combinations not described in mbm29dl64df command definitions are illegal. *2 : both of these reset commands are equivalent. *3 : erase suspend and erase resume command are valid only during a sector erase operations. *4 : this command is valid during fast mode. *5 : the reset from fast mode command is required to return to the read mode when the device is in fast mode. *6 : this command is valid while reset = v id (except during hiddenrom mode) . *7 : sector group address (sga) with (a 6 , a 3 , a 2 , a 1 , a 0 ) = (0, 0, 0, 1, 0) . *8 : the valid address are a 6 to a 0 . *9 : the hiddenrom entry command is required prior to the hiddenrom programming. *10 : this command is valid during hiddenrom mode. *11 : the data f0h is also acceptable. *12 : fourth bus cycle becomes read cycle. notes : address bits a 21 to a 11 = x = h or l for all address commands except or program address (pa) , sector address (sa) , bank address (ba) and sector group address (spa) . bus operations are defined in mbm29dl64df user bus operations (byte = v ih ) and mbm29dl64df user bus operations (byte = v il ) . ra = address of the memory location to be read ia = autoselect read address that sets both the bank address specified at (a 21 , a 20 , a 19 ) and all the other a 6 , a 3 , a 2 , a 1 , a 0 and (a- 1 ) . pa = address of the memory location to be programmed addresses are latched on the falling edge of the write pulse. sa = address of the sector to be erased. the combination of a 21 , a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 and a 12 will uniquely select any sector. ba = bank address. address setted by a 21 , a 20 , a 19 will select bank a, bank b, bank c and bank d. rd = data read from location ra during read operation. id = device code/manufacture code for the address located by ia. pd = data to be programmed at location pa. data is latched on the rising edge of write pulse. spa = sector group address to be protected. set sector group address and (a 6 , a 3 , a 2 , a 1 , a 0 ) = (0, 0, 0, 1, 0) . sga = sector group address. the combination of a 21 to a 12 will uniquely select any sector group. sd = sector group protection verify data. output 01h at protected sector group addresses and output 00h at unprotected sector group addresses. hra = address of the hiddenrom area word mode : 000000h to 00007fh byte mode : 000000h to 0000ffh hrba = bank address of the hiddenrom area (a 21 = a 20 = a 19 = v il ) the system should generate the following address patterns : word mode : 555h or 2aah to addresses a 10 to a 0 byte mode : aaah or 555h to addresses a 10 to a 0 , and a- 1 both read/reset commands are functionally equivalent, resetting the device to the read mode. command sequence bus write cycles reqd first bus write cycle second bus write cycle third bus write cycle fourth bus read/write cycle fifth bus write cycle sixth bus write cycle addr. data addr. data addr. data addr. data addr. data addr. data hiddenrom program * 9, * 10 word 4 555h aah 2aah 55h 555h a0h ( hra ) pa pd ???? byte aaah 555h aaah hiddenrom exit * 10 word 4 555h aah 2aah 55h (hrba) 555h 90h xxxh 00h ???? byte aaah 555h (hrba) aaah
mbm29dl64df -70 12 mbm29dl64df sector group protection verify autoselect codes table *1 : a -1 is for byte mode. at byte mode, dq 14 to dq 8 are high-z and dq 15 is a -1 , the lowest address. *2 : outputs 01h at protected sector group addresses and outputs 00h at unprotected sector group addresses. *3 : when v id is applied to a 9 , both bank 1 and bank 2 are put into autoselect mode, which makes simultaneous operation unable to be executed. consequently, specifying the bank address is not required. however, the bank address needs to be indicated when autoselect mode is read out at command mode, because then it enables to activate simultaneous operation. *4 : at word mode, a read cycle at address (ba) 01h (at byte mode, (ba) 02h) outputs device code. when 227eh (at byte mode, 7eh) is output, it indicates that two additional codes, called extended device codes, will be required. therefore the system may continue reading out these extended device codes at the address of (ba) 0eh (at byte mode, (ba) 1ch) , as well as at (ba) 0fh (at byte mode, (ba) 1eh) . extended autoselect code table (b) : byte mode (w) : word mode hz : high-z * : at byte mode, dq 14 to dq 8 are high-z and dq 15 is a -1 , the lowest address. type a 21 to a 12 a 6 a 3 a 2 a 1 a 0 a -1 * 1 code (hex) manufactures code byte ba* 3 v il v il v il v il v il v il 04h word x 0004h device code byte ba* 3 v il v il v il v il v ih v il 7eh word x 227eh extended device code* 4 byte ba* 3 v il v ih v ih v ih v il v il 02h word x 2202h byte ba* 3 v il v ih v ih v ih v ih v il 01h word x 2201h sector group protection byte sector group addresses v il v il v il v ih v il v il 01h* 2 word x 0001h* 2 type code dq 15 dq 14 dq 13 dq 12 dq 11 dq 10 dq 9 dq 8 dq 7 dq 6 dq 5 dq 4 dq 3 dq 2 dq 1 dq 0 manufactur- ers code (b)* 04h a -1 hzhzhzhzhzhzhz00000100 (w) 0004h 0 0 0 0 0 0 0000000100 device code (b)* 7eh a -1 hzhzhzhzhzhzhz01111110 (w)227eh0 0 1 0 0 0 1001111110 extended device code (b)* 02h a -1 hzhzhzhzhzhzhz00000010 (w) 2202h 0 0 1 0 0 0 1 0 00000010 (b)* 01h a -1 hzhzhzhzhzhzhz00000001 (w) 2201h 0 0 1 0 0 0 1 0 00000001 sector group protection (b)* 01h a -1 hzhzhzhzhzhzhz00000001 (w) 0001h 0 0 0 0 0 0 0000000001
mbm29dl64df -70 13 n flexible sector-erase architecture sector address table (bank a) note : the address range is a 21 : a -1 if in byte mode (byte = v il ) . the address range is a 21 : a 0 if in word mode (byte = v ih ) . bank sector sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range bank address a 21 a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 bank a sa0 0000000000 8/4 000 000h to 001fffh 000000h to 000fffh sa1 0000000001 8/4 002 000h to 003fffh 001000h to 001fffh sa2 0000000010 8/4 004 000h to 005fffh 002000h to 002fffh sa3 0000000011 8/4 006 000h to 007fffh 003000h to 003fffh sa4 0000000100 8/4 008 000h to 009fffh 004000h to 004fffh sa5 0000000101 8/4 00a 000h to 00bfffh 005000h to 005fffh sa6 0000000110 8/4 00c 000h to 00dfffh 006000h to 006fffh sa7 0000000111 8/4 00e000h to 00ffffh 00 7000h to 007fffh sa8 0 0 0 0 0 0 1 x x x 64/32 010000h to 01ffffh 008000h to 00ffffh sa9 0 0 0 0 0 1 0 x x x 64/32 020000h to 02ffffh 010000h to 017fffh sa10 0 0 0 0 0 1 1 x x x 64/32 030000h to 03ffffh 018000h to 01ffffh sa11 0 0 0 0 1 0 0 x x x 64/32 040000h to 04ffffh 020000h to 027fffh sa12 0 0 0 0 1 0 1 x x x 64/32 050000h to 05ffffh 028000h to 02ffffh sa13 0 0 0 0 1 1 0 x x x 64/32 060000h to 06ffffh 030000h to 037fffh sa14 0 0 0 0 1 1 1 x x x 64/32 070000h to 07ffffh 038000h to 03ffffh sa15 0 0 0 1 0 0 0 x x x 64/32 080000h to 08ffffh 040000h to 047fffh sa16 0 0 0 1 0 0 1 x x x 64/32 090000h to 09ffffh 048000h to 04ffffh sa17 0 0 0 1 0 1 0 x x x 64/32 0a0000h to 0affffh 050000h to 057fffh sa18 0 0 0 1 0 1 1 x x x 64/32 0b0000h to 0bffffh 058000h to 05ffffh sa19 0 0 0 1 1 0 0 x x x 64/32 0c0000h to 0cffffh 060000h to 067fffh sa20 0 0 0 1 1 0 1 x x x 64/32 0d0000h to 0dffffh 068000h to 06ffffh sa21 0 0 0 1 1 1 0 x x x 64/32 0e0000h to 0effffh 070000h to 077fffh sa22 0 0 0 1 1 1 1 x x x 64/32 0f0000h to 0fffffh 078000h to 07ffffh
mbm29dl64df -70 14 sector address table (bank b) (continued) bank sector sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range bank address a 21 a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 bank b sa23 0 0 1 0 0 0 0 x x x 64/32 100000h to 10ffffh 080000h to 087fffh sa24 0 0 1 0 0 0 1 x x x 64/32 110000h to 11ffffh 088000h to 08ffffh sa25 0 0 1 0 0 1 0 x x x 64/32 120000h to 12ffffh 090000h to 097fffh sa26 0 0 1 0 0 1 1 x x x 64/32 130000h to 13ffffh 098000h to 09ffffh sa27 0 0 1 0 1 0 0 x x x 64/32 140000h to 14ffffh 0a0000h to 0a7fffh sa28 0 0 1 0 1 0 1 x x x 64/32 150000h to 15ffffh 0a8000h to 0affffh sa29 0 0 1 0 1 1 0 x x x 64/32 160000h to 16ffffh 0b0000h to 0b7fffh sa30 0 0 1 0 1 1 1 x x x 64/32 170000h to 17ffffh 0b8000h to 0bffffh sa31 0 0 1 1 0 0 0 x x x 64/32 180000h to 18ffffh 0c0000h to 0c7fffh sa32 0 0 1 1 0 0 1 x x x 64/32 190000h to 19ffffh 0c8000h to 0cffffh sa33 0 0 1 1 0 1 0 x x x 64/32 1a0000h to 1affffh 0d0000h to 0d7fffh sa34 0 0 1 1 0 1 1 x x x 64/32 1b0000h to 1bffffh 0d8000h to 0dffffh sa35 0 0 1 1 1 0 0 x x x 64/32 1c0000h to 1cffffh 0e0000h to 0e7fffh sa36 0 0 1 1 1 0 1 x x x 64/32 1d0000h to 1dffffh 0e8000h to 0effffh sa37 0 0 1 1 1 1 0 x x x 64/32 1e0000h to 1effffh 0f0000h to 0f7fffh sa38 0 0 1 1 1 1 1 x x x 64/32 1f0000h to 1fffffh 0f8000h to 0fffffh sa39 0 1 0 0 0 0 0 x x x 64/32 200000h to 20ffffh 100000h to 107fffh sa40 0 1 0 0 0 0 1 x x x 64/32 210000h to 21ffffh 108000h to 10ffffh sa41 0 1 0 0 0 1 0 x x x 64/32 220000h to 22ffffh 110000h to 117fffh sa42 0 1 0 0 0 1 1 x x x 64/32 230000h to 23ffffh 118000h to 11ffffh sa43 0 1 0 0 1 0 0 x x x 64/32 240000h to 24ffffh 120000h to 127fffh sa44 0 1 0 0 1 0 1 x x x 64/32 250000h to 25ffffh 128000h to 12ffffh sa45 0 1 0 0 1 1 0 x x x 64/32 260000h to 26ffffh 130000h to 137fffh sa46 0 1 0 0 1 1 1 x x x 64/32 270000h to 27ffffh 138000h to 13ffffh sa47 0 1 0 1 0 0 0 x x x 64/32 280000h to 28ffffh 140000h to 147fffh sa48 0 1 0 1 0 0 1 x x x 64/32 290000h to 29ffffh 148000h to 14ffffh sa49 0 1 0 1 0 1 0 x x x 64/32 2a0000h to 2affffh 150000h to 157fffh sa50 0 1 0 1 0 1 1 x x x 64/32 2b0000h to 2bffffh 158000h to 15ffffh sa51 0 1 0 1 1 0 0 x x x 64/32 2c0000h to 2cffffh 160000h to 167fffh sa52 0 1 0 1 1 0 1 x x x 64/32 2d0000h to 2dffffh 168000h to 16ffffh sa53 0 1 0 1 1 1 0 x x x 64/32 2e0000h to 2effffh 170000h to 177fffh
mbm29dl64df -70 15 (continued) note : the address range is a 21 : a -1 if in byte mode (byte = v il ) . the address range is a 21 : a 0 if in word mode (byte = v ih ) . bank sector sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range bank address a 21 a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 bank b sa54 0 1 0 1 1 1 1 x x x 64/32 2f0000h to 2fffffh 178000h to 17ffffh sa55 0 1 1 0 0 0 0 x x x 64/32 300000h to 30ffffh 180000h to 187fffh sa56 0 1 1 0 0 0 1 x x x 64/32 310000h to 31ffffh 188000h to 18ffffh sa57 0 1 1 0 0 1 0 x x x 64/32 320000h to 32ffffh 190000h to 197fffh sa58 0 1 1 0 0 1 1 x x x 64/32 330000h to 33ffffh 198000h to 19ffffh sa59 0 1 1 0 1 0 0 x x x 64/32 340000h to 34ffffh 1a0000h to 1a7fffh sa60 0 1 1 0 1 0 1 x x x 64/32 350000h to 35ffffh 1a8000h to 1affffh sa61 0 1 1 0 1 1 0 x x x 64/32 360000h to 36ffffh 1b0000h to 1b7fffh sa62 0 1 1 0 1 1 1 x x x 64/32 370000h to 37ffffh 1b8000h to 1bffffh sa63 0 1 1 1 0 0 0 x x x 64/32 380000h to 38ffffh 1c0000h to 1c7fffh sa64 0 1 1 1 0 0 1 x x x 64/32 390000h to 39ffffh 1c8000h to 1cffffh sa65 0 1 1 1 0 1 0 x x x 64/32 3a0000h to 3affffh 1d0000h to 1d7fffh sa66 0 1 1 1 0 1 1 x x x 64/32 3b0000h to 3bffffh 1d8000h to 1dffffh sa67 0 1 1 1 1 0 0 x x x 64/32 3c0000h to 3cffffh 1e0000h to 1e7fffh sa68 0 1 1 1 1 0 1 x x x 64/32 3d0000h to 3dffffh 1e8000h to 1effffh sa69 0 1 1 1 1 1 0 x x x 64/32 3e0000h to 3effffh 1f0000h to 1f7fffh sa70 0 1 1 1 1 1 1 x x x 64/32 3f0000h to 3fffffh 1f8000h to 1fffffh
mbm29dl64df -70 16 sector address table (bank c) (continued) bank sector sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range bank address a 21 a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 bank c sa71 1 0 0 0 0 0 0 x x x 64/32 400000h to 40ffffh 200000h to 207fffh sa72 1 0 0 0 0 0 1 x x x 64/32 410000h to 41ffffh 208000h to 20ffffh sa73 1 0 0 0 0 1 0 x x x 64/32 420000h to 42ffffh 210000h to 217fffh sa74 1 0 0 0 0 1 1 x x x 64/32 430000h to 43ffffh 218000h to 21ffffh sa75 1 0 0 0 1 0 0 x x x 64/32 440000h to 44ffffh 220000h to 227fffh sa76 1 0 0 0 1 0 1 x x x 64/32 450000h to 45ffffh 228000h to 22ffffh sa77 1 0 0 0 1 1 0 x x x 64/32 460000h to 46ffffh 230000h to 237fffh sa78 1 0 0 0 1 1 1 x x x 64/32 470000h to 47ffffh 238000h to 23ffffh sa79 1 0 0 1 0 0 0 x x x 64/32 480000h to 48ffffh 240000h to 247fffh sa80 1 0 0 1 0 0 1 x x x 64/32 490000h to 49ffffh 248000h to 24ffffh sa81 1 0 0 1 0 1 0 x x x 64/32 4a0000h to 4affffh 250000h to 257fffh sa82 1 0 0 1 0 1 1 x x x 64/32 4b0000h to 4bffffh 258000h to 25ffffh sa83 1 0 0 1 1 0 0 x x x 64/32 4c0000h to 4cffffh 260000h to 267fffh sa84 1 0 0 1 1 0 1 x x x 64/32 4d0000h to 4dffffh 268000h to 26ffffh sa85 1 0 0 1 1 1 0 x x x 64/32 4e0000h to 4effffh 270000h to 277fffh sa86 1 0 0 1 1 1 1 x x x 64/32 4f0000h to 4fffffh 278000h to 27ffffh sa87 1 0 1 0 0 0 0 x x x 64/32 500000h to 50ffffh 280000h to 287fffh sa88 1 0 1 0 0 0 1 x x x 64/32 510000h to 51ffffh 288000h to 28ffffh sa89 1 0 1 0 0 1 0 x x x 64/32 520000h to 52ffffh 290000h to 297fffh sa90 1 0 1 0 0 1 1 x x x 64/32 530000h to 53ffffh 298000h to 29ffffh sa91 1 0 1 0 1 0 0 x x x 64/32 540000h to 54ffffh 2a0000h to 2a7fffh sa92 1 0 1 0 1 0 1 x x x 64/32 550000h to 55ffffh 2a8000h to 2affffh sa93 1 0 1 0 1 1 0 x x x 64/32 560000h to 56ffffh 2b0000h to 2b7fffh sa94 1 0 1 0 1 1 1 x x x 64/32 570000h to 57ffffh 2b8000h to 2bffffh sa95 1 0 1 1 0 0 0 x x x 64/32 580000h to 58ffffh 2c0000h to 2c7fffh sa96 1 0 1 1 0 0 1 x x x 64/32 590000h to 59ffffh 2c8000h to 2cffffh sa97 1 0 1 1 0 1 0 x x x 64/32 5a0000h to 5affffh 2d0000h to 2d7fffh sa98 1 0 1 1 0 1 1 x x x 64/32 5b0000h to 5bffffh 2d8000h to 2dffffh sa99 1 0 1 1 1 0 0 x x x 64/32 5c0000h to 5cffffh 2e0000h to 2e7fffh sa100 1 0 1 1 1 0 1 x x x 64/32 5d0000h to 5dffffh 2e8000h to 2effffh sa101 1 0 1 1 1 1 0 x x x 64/32 5e0000h to 5effffh 2f0000h to 2f7fffh sa102 1 0 1 1 1 1 1 x x x 64/32 5f0000h to 5fffffh 2f8000h to 2fffffh
mbm29dl64df -70 17 (continued) note : the address range is a 21 : a -1 if in byte mode (byte = v il ) . the address range is a 21 : a 0 if in word mode (byte = v ih ) . bank sector sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range bank address a 21 a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 bank c sa103 1 1 0 0 0 0 0 x x x 64/32 600000h to 60ffffh 300000h to 307fffh sa104 1 1 0 0 0 0 1 x x x 64/32 610000h to 61ffffh 308000h to 30ffffh sa105 1 1 0 0 0 1 0 x x x 64/32 620000h to 62ffffh 310000h to 317fffh sa106 1 1 0 0 0 1 1 x x x 64/32 630000h to 63ffffh 318000h to 31ffffh sa107 1 1 0 0 1 0 0 x x x 64/32 640000h to 64ffffh 320000h to 327fffh sa108 1 1 0 0 1 0 1 x x x 64/32 650000h to 65ffffh 328000h to 32ffffh sa109 1 1 0 0 1 1 0 x x x 64/32 660000h to 66ffffh 330000h to 337fffh sa110 1 1 0 0 1 1 1 x x x 64/32 670000h to 67ffffh 338000h to 33ffffh sa111 1 1 0 1 0 0 0 x x x 64/32 680000h to 68ffffh 340000h to 347fffh sa112 1 1 0 1 0 0 1 x x x 64/32 690000h to 69ffffh 348000h to 34ffffh sa113 1 1 0 1 0 1 0 x x x 64/32 6a0000h to 6affffh 350000h to 357fffh sa114 1 1 0 1 0 1 1 x x x 64/32 6b0000h to 6bffffh 358000h to 35ffffh sa115 1 1 0 1 1 0 0 x x x 64/32 6c0000h to 6cffffh 360000h to 367fffh sa116 1 1 0 1 1 0 1 x x x 64/32 6d0000h to 6dffffh 368000h to 36ffffh sa117 1 1 0 1 1 1 0 x x x 64/32 6e0000h to 6effffh 370000h to 377fffh sa118 1 1 0 1 1 1 1 x x x 64/32 6f0000h to 6fffffh 378000h to 37ffffh
mbm29dl64df -70 18 sector address table (bank d) note : the address range is a 21 : a -1 if in byte mode (byte = v il ) . the address range is a 21 : a 0 if in word mode (byte = v ih ) . bank sector sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range bank address a 21 a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 bank d sa119 1 1 1 0 0 0 0 x x x 64/32 700000h to 70ffffh 380000h to 387fffh sa120 1 1 1 0 0 0 1 x x x 64/32 710000h to 71ffffh 388000h to 38ffffh sa121 1 1 1 0 0 1 0 x x x 64/32 720000h to 72ffffh 390000h to 397fffh sa122 1 1 1 0 0 1 1 x x x 64/32 730000h to 73ffffh 398000h to 39ffffh sa123 1 1 1 0 1 0 0 x x x 64/32 740000h to 74ffffh 3a0000h to 3a7fffh sa124 1 1 1 0 1 0 1 x x x 64/32 750000h to 75ffffh 3a8000h to 3affffh sa125 1 1 1 0 1 1 0 x x x 64/32 760000h to 76ffffh 3b0000h to 3b7fffh sa126 1 1 1 0 1 1 1 x x x 64/32 770000h to 77ffffh 3b8000h to 3bffffh sa127 1 1 1 1 0 0 0 x x x 64/32 780000h to 78ffffh 3c0000h to 3c7fffh sa128 1 1 1 1 0 0 1 x x x 64/32 790000h to 79ffffh 3c8000h to 3cffffh sa129 1 1 1 1 0 1 0 x x x 64/32 7a0000h to 7affffh 3d0000h to 3d7fffh sa130 1 1 1 1 0 1 1 x x x 64/32 7b0000h to 7bffffh 3d8000h to 3dffffh sa131 1 1 1 1 1 0 0 x x x 64/32 7c0000h to 7cffffh 3e0000h to 3e7fffh sa132 1 1 1 1 1 0 1 x x x 64/32 7d0000h to 7dffffh 3e8000h to 3effffh sa133 1 1 1 1 1 1 0 x x x 64/32 7e0000h to 7effffh 3f0000h to 3f7fffh sa134 1111111000 8/4 7f0 000h to 7f1fffh 3f8000h to 3f8fffh sa135 1111111001 8/4 7f2 000h to 7f3fffh 3f9000h to 3f9fffh sa136 1111111010 8/4 7f4 000h to 7f5fffh 3fa000h to 3fafffh sa137 1111111011 8/4 7f6 000h to 7f7fffh 3fb000h to 3fbfffh sa138 1111111100 8/4 7f8 000h to 7f9fffh 3fc000h to 3fcfffh sa139 1111111101 8/4 7fa 000h to 7fbfffh 3fd000h to 3fdfffh sa140 1111111110 8/4 7fc 000h to 7fdfffh 3fe000h to 3fefffh sa141 1111111111 8/4 7fe000h to 7fffffh3ff000h to 3fffffh
mbm29dl64df -70 19 sector group address table (continued) sector group a 21 a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 sectors sga0 0000000000 sa0 sga1 0000000001 sa1 sga2 0000000010 sa2 sga3 0000000011 sa3 sga4 0000000100 sa4 sga5 0000000101 sa5 sga6 0000000110 sa6 sga7 0000000111 sa7 sga8 00000 01 xxx sa8 to sa10 10 11 sga9 00001 xxxxxsa11 to sa14 sga10 00010 xxxxxsa15 to sa18 sga11 00011 xxxxxsa19 to sa22 sga12 00100 xxxxxsa23 to sa26 sga13 00101 xxxxxsa27 to sa30 sga14 00110 xxxxxsa31 to sa34 sga15 00111 xxxxxsa35 to sa38 sga16 01000 xxxxxsa39 to sa42 sga17 01001 xxxxxsa43 to sa46 sga18 01010 xxxxxsa47 to sa50 sga19 01011 xxxxxsa51 to sa54 sga20 01100 xxxxxsa55 to sa58 sga21 01101 xxxxxsa59 to sa62 sga22 01110 xxxxxsa63 to sa66 sga23 01111 xxxxxsa67 to sa70
mbm29dl64df -70 20 (continued) sector group a 21 a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 sectors sga24 10000 xxxxxsa71 to sa74 sga25 10001 xxxxxsa75 to sa78 sga26 10010 xxxxxsa79 to sa82 sga27 10011 xxxxxsa83 to sa86 sga28 10100 xxxxxsa87 to sa90 sga29 10101 xxxxxsa91 to sa94 sga30 10110 xxxxxsa95 to sa98 sga31 10111 xxxxxsa99 to sa102 sga32 11000 xxxxxsa103 to sa106 sga33 11001 xxxxxsa107 to sa110 sga34 11010 xxxxxsa111 to sa114 sga35 11011 xxxxxsa115 to sa118 sga36 11100 xxxxxsa119 to sa122 sga37 11101 xxxxxsa123 to sa126 sga38 11110 xxxxxsa127 to sa130 sga39 11111 00 x x x sa131 to sa133 01 10 sga40 1111111000 sa134 sga41 1111111001 sa135 sga42 1111111010 sa136 sga43 1111111011 sa137 sga44 1111111100 sa138 sga45 1111111101 sa139 sga46 1111111110 sa140 sga47 1111111111 sa141
mbm29dl64df -70 21 common flash memory interface code table (continued) description a 6 to a 0 dq 15 to dq 0 query-unique ascii string qry 10h 11h 12h 0051h 0052h 0059h primary oem command set 02h : amd/fj standard type 13h 14h 0002h 0000h address for primary extended table 15h 16h 0040h 0000h alternate oem command set (00h = not applicable) 17h 18h 0000h 0000h address for alternate oem extended table 19h 1ah 0000h 0000h v cc min (write/erase) dq 7 to dq 4 : 1 v, dq 3 to dq 0 : 100 mv 1bh 0027h v cc max (write/erase) dq 7 to dq 4 : 1 v, dq 3 to dq 0 : 100 mv 1ch 0036h v pp min voltage 1dh 0000h v pp max voltage 1eh 0000h typical timeout per single byte/word write 2 n m s 1fh 0004h typical timeout for min size buffer write 2 n m s 20h 0000h typical timeout per individual sector erase 2 n ms 21h 000ah typical timeout for full chip erase 2 n ms 22h 0000h max timeout for byte/word write 2 n times typical 23h 0005h max timeout for buffer write 2 n times typical 24h 0000h max timeout per individual sector erase 2 n times typical 25h 0004h max timeout for full chip erase 2 n times typical 26h 0000h device size = 2 n byte 27h 0017h flash device interface description 02h : 8 / 16 28h 29h 0002h 0000h max number of bytes in multi-byte write = 2 n 2ah 2bh 0000h 0000h number of erase block regions within device 2ch 0003h erase block region 1 information bit 15 to bit 0 : y = number of sectors bit 31 to bit 16 : z = size (z 256 bytes) 2dh 2eh 2fh 30h 0007h 0000h 0020h 0000h erase block region 2 information bit 15 to bit 0 : y = number of sectors bit 31 to bit 16 : z = size (z 256 bytes) 31h 32h 33h 34h 007dh 0000h 0000h 0001h
mbm29dl64df -70 22 (continued) description a 6 to a 0 dq 15 to dq 0 erase block region 3 information bit 15 to bit 0 : y = number of sectors bit 31 to bit 16 : z = size (z 256 bytes) 35h 36h 37h 38h 0007h 0000h 0020h 0000h query-unique ascii string pri 40h 41h 42h 0050h 0052h 0049h major version number, ascii 43h 0031h minor version number, ascii 44h 0033h address for command write and process technology dq 1 , dq 0 : address requied for command write (00h : requied) 04h : required and 0.17 m m technology dq 7 to dq 2 : 0.17 m m process technology 45h 0004h erase suspend 02h = to read & write 46h 0002h sector protection 00h = not supported x = number of sectors per group 47h 0001h sector temporary unprotection 01h = supported 48h 0001h sector protection algorithm 49h 0004h dual operation 00h = not supported x = total number of sectors in all banks except bank 1 4ah 0077h burst mode type 00h = not supported 4bh 0000h page mode type 00h = not supported 4ch 0000h v acc (acceleration) supply minimum dq 7 to dq 4 : 1 v, dq 3 to dq 0 : 100 mv 4dh 0085h v acc (acceleration) supply maximum dq 7 to dq 4 : 1 v, dq 3 to dq 0 : 100 mv 4eh 0095h boot type 4fh 0001h program suspend 01h = supported 50h 0001h bank organization x = number of banks 57h 0004h bank a region information x = number of sectors in bank a 58h 0017h bank b region information x = number of sectors in bank b 59h 0030h bank c region information x = number of sectors in bank c 5ah 0030h bank d region information x = number of sectors in bank d 5bh 0017h
mbm29dl64df -70 23 n functional description simultaneous operation the device features functions that enable data reading of one memory bank while a program or erase operation is in progress in the other memory bank (simultaneous operation) , in addition to conventional features (read, program, erase, erase-suspend read, and erase-suspend program) . the bank is selected by bank address (a 21 , a 20 , a 19 ) with zero latency. the device consists of the following four banks : bank a : 8 8 kb and 15 64 kb; bank b : 48 64 kb; bank c : 48 64 kb; bank d : 8 8 kb and 15 64 kb. the device can execute simultaneous operations between bank 1, a bank chosen from among the four banks, and bank 2, a bank consisting of the three remaining banks (see flexbank tm architecture.) this is what we call flexbank, for example, the rest of banks b, c and d to let the system read while bank a is in the process of program (or erase) operation. however the different types of operations for the three banks are not allowed, e.g., bank a writing, bank b erasing, and bank c reading out. with this flexbank, as described in example of virtual banks combination, the system gets to select from four combinations of data volume for bank 1 and bank 2, which works well to meet the system requirement. the simultaneous operation cannot execute multi- function mode in the same bank. simultaneous operation shows the possible combinations for simultaneous operation (refer to (8) bank-to-bank read/write timing diagram in n timing diagram.) flexbank tm architecture table example of virtual banks combination table note : when multiple sector erase over several banks is operated, the system cannot read out of the bank to which a sector being erased belongs. for example, suppose that erasing is taking place at both bank a and bank b, neither bank a nor bank b is read out they output the sequence flag once they are selected. meanwhile the system would get to read from either bank c or bank d. bank splits bank 1 bank 2 volume combination volume combination 1 8 mbit bank a 56 mbit bank b, c, d 2 24 mbit bank b 40 mbit bank a, c, d 3 24 mbit bank c 40 mbit bank a, b, d 4 8 mbit bank d 56 mbit bank a, b, c bank splits bank 1 bank 2 volume combination sector size volume combination sector size 18 mbit bank a 8 8 kbyte/4 kword + 15 64 kbyte/32 kword 56 mbit bank b + bank c + bank d 8 8 kbyte/4 kword + 111 64 kbyte/32 kword 216 mbit bank a + bank d 16 8 kbyte/4 kword + 30 64 kbyte/32 kword 48 mbit bank b + bank c 96 64 kbyte/32 kword 3 24 mbit bank b 48 64 kbyte/32 kword 40 mbit bank a + bank c + bank d 16 8 kbyte/4 kword + 78 64 kbyte/32 kword 432 mbit bank a + bank b 8 8 kbyte/4 kword + 63 64 kbyte/32 kword 32 mbit bank c + bank d 8 8 kbyte/4 kword + 63 64 kbyte/32 kword
mbm29dl64df -70 24 simultaneous operation table * : by writing erase suspend command on the bank address of sector being erased, the erase operation becomes suspended so that it enables reading from or programming the remaining sectors. note : bank 1 and bank 2 are divided for the sake of convenience at simultaneous operation. the bank consists of 4 banks, bank a, bank b, bankc and bank d. bank address (ba) means to specify each of the banks. read mode the device has two control functions required to obtain data at the outputs. ce is the power control and used for a device selection. oe is the output control and used to gate data to the output pins. address access time (t acc ) is equal to the delay from stable addresses to valid output data. the chip enable access time (t ce ) is the delay from stable addresses and stable ce to valid data at the output pins. the output enable access time is the delay from the falling edge of oe to valid data at the output pins, assuming the addresses have been stable for at least t acc -t oe time. when reading out data without changing addresses after power-up, it is required to input hardware reset or to change ce pin from h to l standby mode there are two ways to implement the standby mode on the device, one using both the ce and reset pins, and the other via the reset pin only. when using both pins, cmos standby mode is achieved with ce and reset input held at v cc 0.3 v. under this condition the current consumed is less than 5 m a max. during embedded algorithm operation, v cc active current (i cc2 ) is required even when ce = h. the device can be read with standard access time (t ce ) from either of these standby modes. when using the reset pin only, cmos standby mode is achieved with reset input held at v ss 0.3 v (ce = h or l) . under this condition the current consumed is less than 5 m a max. once the reset pin is set high, the device requires t rh as a wake-up time for output to be valid for read access. during standby mode, the output is in the high impedance state regardless of oe input. automatic sleep mode automatic sleep mode works to restrain power consumption during read-out of device data. this is useful in applications such as handy terminal which requires low power consumption. to activate this mode, the device automatically switches itself to low power mode when the device addresses remain stable during after 150 ns from data valid. it is not necessary to control ce , we and oe in this mode. in this mode the current consumed is typically 1 m a (cmos level) . during simultaneous operation, v cc active current (i cc2 ) is required. since the data are latched during this mode, the data are continuously read out. when the addresses are changed, the mode is automatically canceled and the device reads the data for changed addresses. case bank 1 status bank 2 status 1 read mode read mode 2 read mode autoselect mode 3 read mode program mode 4 read mode erase mode * 5 autoselect mode read mode 6 program mode read mode 7 erase mode * read mode
mbm29dl64df -70 25 output disable with the oe input at a logic high level (v ih ) , output from the device is disabled. this causes the output pins to be in a high impedance state. autoselect autoselect mode allows reading out of binary code and identifies its manufacturer and type.it is intended for use by programming equipment for the purpose of automatically matching the device to be programmed with its corresponding programming algorithm. this mode is functional over the entire temperature range of the device. to activate this mode, the programming equipment must force v id on address pin a 9 . three identifier bytes may then be sequenced from the device outputs by toggling addresses. all addresses can be either high or low except a 6 , a 3 , a 2 , a 1 , a 0 and (a -1 ) see user bus operations. the manufacturer and device codes may also be read via the command register, for instances when the device is erased or programmed in a system without access to high voltage on the a 9 pin. the command sequence is illustrated in command definitions. in the command autoselect mode, the bank addresses ba; (a 21 , a 20 , a 19 ) must point to a specific bank during the third write bus cycle of the autoselect command. then the autoselect data will be read from that bank while array data can be read from the other bank. in word mode, a read cycle from address 00h returns the manufacturers code (fujitsu = 04h) . a read cycle at address 01h outputs device code. when 227eh is output, it indicates that two additional codes, called extended device codes is required. therefore the system may continue reading out these extended device codes at addresses of 0eh and 0fh. notice that the above applies to word mode; the addresses and codes differ from those of byte mode (refer to sector group protection verify autoselect codes table and extended autoselect code table in n device bus operation. in the case of applying v id on a 9 , as both bank 1 and bank 2 enter autoselect mode, simultanous operation cannot be executed. write device erasure and programming are accomplished via the command register. the contents of the register serve as input to the internal state machine. the state machine output dictates the device function. the command register itself does not occupy any addressable memory location. the register is a latch used to store the commands, along with the address and data information needed to execute the command. the com- mand register is written by bringing we to v il , while ce is at v il and oe is at v ih . addresses are latched on the falling edge of we or ce , whichever starts later, while data is latched on the rising edge of we or ce , whichever starts first. standard microprocessor write timings are used. refer to n ac write characteristics and erase/programming waveforms for specific timing parameters. sector group protection the device features hardware sector group protection. this feature disables both program and erase operations in any combination of forty eight sector groups of memory. see sector group address table. the users side can use sector group protection using programming equipment. the device is shipped with all sector groups unprotected. to activate it, the programming equipment must force v id on address pin a 9 and control pin oe , ce = v il and a 6 = a 3 = a 2 = a 0 = v il , a 1 = v ih . the sector group addresses (a 21 , a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 and a 12 ) should be set to the sector to be protected. sector address tables (bank a to bank d) define the sector address for each of the one hundred forty-two (142) individual sectors, and sector group address table defines the sector group address for each of the forty eight (48) individual group sectors. programming of the protection circuitry begins on the falling edge of the we pulse and is terminated with the rising edge of the same. sector group addresses must be held constant during the we pulse. see sector group protection waveforms and algorithms. to verify programming of the protection circuitry, the programming equipment must force v id on address pin a 9 with ce and oe at v il and we at v ih . scanning the sector group addresses (a 21 , a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 and a 12 ) while (a 6 , a 3 , a 2 , a 1 , a 0 ) = (0, 0, 0, 1, 0) produces a logica 1 code at device output dq 0 for a protected sector. otherwise the device produces 0 for unprotected sectors. in this mode, the lower order
mbm29dl64df -70 26 addresses, except for a 6 , a 3 , a 2 , a 1 and a 0 are dont cares. address locations with a 1 = v il are reserved for autoselect manufacturer and device codes. a -1 requires applying to v il on byte mode. whether the sector group is protected in the system can be determined by writing an autoselect command. performing a read operation at the address location (ba) xx02h, where the higher order addresses (a 21 , a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 , and a 12 ) are the desired sector group address, will produce a logical 1 at dq 0 for a protected sector group. note that the bank addresses (a 21 , a 20 , a 19 ) must be pointing to a specific bank during the third write bus cycle of the autoselect command. then the autoselect data can be read from that bank while array data can still be read from the other bank. to read autoselect data from the other bank, it must be reset to read mode and then write the autoselect command to the other bank. see sector group protection verify autoselect codes. temporary sector group unprotection this feature allows temporary unprotection of previously protected sector groups of the device in order to change data. the sector group unprotection mode is activated by setting the reset pin to high voltage (v id ) . during this mode, formerly protected sector groups can be programmed or erased by selecting the sector group ad- dresses. once the v id is taken away from the reset pin, all the previously protected sector groups will be protected again. refer to (6) temporary sector group unprotection algorithm in n flow chrat. reset hardware reset the device is reset by driving the reset pin to v il . the reset pin works pulse requirement and has to be kept low (v il ) for at least t rp in order to properly reset the internal state machine. any operation in the process of being executed is terminated and the internal state machine is reset to the read mode t ready after the reset pin is driven low. furthermore once the reset pin goes high the device requires an additional t rh before it allows read access. when the reset pin is low, the device will be in the standby mode for the duration of the pulse and all the data output pins are tri-stated. if a hardware reset occurs during a program or erase operation, the data at that particular location is corrupted. please note that the ry/by output signal should be ignored during the reset pulse. see (11) reset , ry/by timing diagram in n timing diagram for the timing diagram. refer to temporary sector group unprotection for additional functionality. byte/word configuration byte pin selects byte (8-bit) mode or word (16-bit) mode for the device. when this pin is driven high, the device operates in word (16-bit) mode. data is read and programmed at dq 15 to dq 0 . when this pin is driven low, the device operates in byte (8-bit) mode. in this mode the dq 15 /a -1 pin becomes the lowest address bit, and dq 14 to dq 8 bits are tri-stated. however the command bus cycle is always an 8-bit operation and hence commands are written at dq 7 to dq 0 and dq 15 to dq 8 bits are ignored. refer to timing diagram for word mode/byte mode configuration. boot block sector protection the write protection function provides a hardware method of protecting certain boot sectors without using v id . this function is one of two provided by the wp /acc pin. if the system asserts v il on the wp /acc pin, the device disables program and erase functions in the two outermost 8 kbytes on both ends of boot sectors (sa0, sa1, sa140, and sa141) independently of whether those sectors are protected or unprotected using the method described in sector group protection. if the system asserts v ih on the wp /acc pin, the device reverts to whether the two outermost 8 kbyte on both ends of boot sectors were last set to be protected or unprotected. sector group protection or unprotection for these four sectors depends on whether they ware last protected or unprotected using the method described in sector group protection.
mbm29dl64df -70 27 accelerated program operation the device offers accelerated program operation which enables programming in high speed. if the system asserts v acc to the wp /acc pin, the device automatically enters the acceleration mode and the time required for program operation reduces to about 60 % . this function is primarily intended to allow high speed programming, so caution is needed as the sector group temporarily becomes unprotected. the system uses a fast program command sequence when programming during acceleration mode. set command to fast mode and reset command from fast mode are not necessary. when the device enters the acceleration mode, the device is automatically set to fast mode. therefore the present sequence could be used for programming and detection of completion during acceleration mode. removing v acc from the wp /acc pin returns the device to normal operation. do not remove v acc from wp / acc pin while programming. see (18) accelerated program timing diagram in n timing diagram. erase operation at acceleration mode is strictly prohibited.
mbm29dl64df -70 28 n command definitions device operations are selected by writing specific address and data sequences into the command register. some commands require bank address (ba) input. when command sequences are input into a bank reading, the commands have priority over the reading. n device bus operation table shows the valid register command sequences. note that the erase suspend (b0h) and erase resume (30h) commands are valid only while the sector erase operation is in progress. also the program suspend (b0h) and program resume (30h) commands are valid only while the program operation is in progress. furthermore read/reset commands are functionally equivalent, resetting the device to the read mode. note that commands are always written at dq 7 to dq 0 and dq 15 to dq 8 bits are ignored. read/reset command in order to return from autoselect mode or exceeded timing limits (dq 5 = 1) to read/reset mode, the read/ reset operation is initiated by writing the read/reset command sequence into the command register. micro- processor read cycles retrieve array data from the memory. the device remains enabled for reads until the command register contents are altered. the device automatically powers-up in the read/reset state. in this case a command sequence is not required in order to read data. standard microprocessor read cycles will retrieve array data. this default value ensures that no spurious alteration of the memory content occurs during the power transition. refer to n ac charac- teristics and n timing diagram for the specific timing parameters. autoselect command flash memories are designed for use in applications where the local cpu alters memory contents. therefore manufacture and device codes must be accessible while the device resides in the target system. prom pro- grammers typically access the signature codes by raising a 9 to a higher voltage. however multiplexing high voltage onto the address lines is not generally desired system design practice. the device contains autoselect command operation to supplement traditional prom programming methodology. the operation is initiated by writing the autoselect command sequence into the command register. the autoselect command sequence is initiated first by writing two unlock cycles. this is followed by a third write cycle that contains the bank address (ba) and the autoselect command. then the manufacture and device codes can be read from the bank, and actual data from the memory cell can be read from another bank. the higher order address (a 21 , a 20 , a 19 ) required for reading out the manufacture and device codes demands the bank address (ba) set at the third write cycle. following the command write, in word mode, a read cycle from address (ba) 00h returns the manufacturers code (fujitsu = 04h) . and a read cycle at address (ba) 01h outputs device code. when 227eh was output, this indicates that two additional codes, called extended device codes will be required. therefore the system may continue reading out these extended device codes at the address of (ba) 0eh, as well as at (ba) 0fh. notice that the above applies to word mode. the addresses and codes differ from those of byte mode (refer to mbm29dl64df sector group protection verify autoselect codes and extended autoselect code table in n device bus operation. ) the sector state (protection or unprotection) will be informed by address (ba) 02h for 16 ( (ba) 04h for 8) . scanning the sector group addresses (a 21 , a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 , and a 12 ) while (a 6 , a 3 , a 2 , a 1 , a 0 ) = (0, 0, 0, 1, 0) produces a logic 1 at device output dq 0 for a protected sector group. the programming verification should be performed by verifying sector group protection on the protected sector (see user bus operations tables. the manufacture and device codes can be read from the selected bank. to read the manufacture and device codes and sector group protection status from a non-selected bank, it is necessary to write the read/reset command sequence into the register. autoselect command should then be written into the bank to be read. if the software (program code) for autoselect command is stored in the flash memory, the device and manu- facture codes should be read from the other bank, which does not contain the software.
mbm29dl64df -70 29 to terminate the operation, write the read/reset command sequence into the register. to execute the autoselect command during the operation, read/reset command sequence must be written before the autoselect com- mand. byte/word programming the device is programmed on a byte-by-byte (or word-by-word) basis. programming is a four bus cycle operation. there are two unlock write cycles. these are followed by the program set-up command and data write cycles. addresses are latched on the falling edge of ce or we , whichever happens later, and the data is latched on the rising edge of ce or we , whichever happens first. the rising edge of ce or we (whichever happens first) starts programming. upon executing the embedded program algorithm command sequence, the system is not required to provide further controls or timings. the device automatically provides adequate internally generated program pulses and verify programmed cell margin. the system can determine program operation status by using dq 7 (data polling) , dq 6 (toggle bit) or ry/by . the data polling and toggle bit must be performed at the memory location being programmed. the automatic programming operation is completed when the data on dq 7 is equivalent to data written to this bit at which the device returns to the read mode and addresses are no longer latched (see hardware sequence flags) . therefore the device requires that a valid address to the device be supplied by the system in this particular instance. hence data polling must be performed at the memory location being programmed. if hardware reset occurs during the programming operation, the data being written is not guaranteed. programming is allowed in any sequence and across sector boundaries. beware that a data 0 cannot be programmed back to a 1. attempting to do so may either hang up the device or result in an apparent success according to the data polling algorithm but a read from read/reset mode will show that the data is still 0. only erase operations can convert from 0s to 1s. (1) embedded program tm algorithm in n flow chart illustrates the embedded program tm algorithm using typical command strings and bus operations. program suspend/resume the program suspend command allows the system to interrupt a program operation so that data can be read from any address. writing the program suspend command (b0h) during the embedded program operation immediately suspends the programming. the program suspend command is issued during programming op- eration as well while an erase is suspended. the bank addresses of sector being programmed should be set when writing the program suspend command. when the program suspend command is written during programming process, the device halts the program operation within 1 m s and updates the status bits. after the program operation is suspended, the system can read data from any address. the data at program- suspended address is not valid. normal read timing and command definitions apply. after the program resume command (30h) is written, the device reverts to programming. the bank addresses of sectors being suspended should be set when writing the program resume command. the system can determine the program operation status using the dq 7 or dq 6 status bits, just as in the standard program operation. see write operation status for more information. the system may also write the autoselect command sequence when the device in the program suspend mode. the device allows reading autoselect codes at the addresses within programming sectors, since the codes are not stored in the memory. when the device exits from the autoselect mode, the device reverts to the program suspend mode, and is ready for another valid operation. see autoselect command for more information. the system must write the program resume command (address bits are bank address) to exit from the program suspend mode and continue the programming operation. further writes of the resume command are ignored. another program suspend command can be written after the device resumes programming.
mbm29dl64df -70 30 chip erase chip erase is a six bus cycle operation. there are two unlock write cycles. these are followed by writing the set-up command. two more unlock write cycles are then followed by the chip erase command. chip erase does not require the user to program prior to erase. upon executing the embedded erase algorithm command sequence, the device automatically programs and verifies the entire memory for an all-zero data pattern prior to electrical erase (preprogram function) . the system is not required to provide any controls or timings during these operations. the system can determine the erase operation status by using dq 7 (data polling) , dq 6 (toggle bit) or ry/by . the chip erase begins on the rising edge of the last ce or we , whichever happens first in the command sequence, and terminates when the data on dq 7 is 1 (see write operation status section) , at which the device returns to the read mode. chip erase time : sector erase time all sectors + chip program time (preprogramming) (2) embedded erase tm algorithm in n flow chart illustrates the embedded erase tm algorithm using typical command strings and bus operations. sector erase sector erase is a six bus cycle operation. there are two unlock write cycles. these are followed by writing the set-up command. two more unlock write cycles are then followed by the sector erase command. the sector address (any address location within the desired sector) is latched on the falling edge of ce or we , whichever starts later, while the command (data = 30h) is latched on the rising edge of ce or we , whichever starts first. after time-out of t tow from the rising edge of the last sector erase command, the sector erase operation begins. multiple sectors are erased concurrently by writing the six bus cycle operations on command definitions. this sequence is followed by writes of the sector erase command to addresses in other sectors desired to be concurrently erased. the time between writes must be less than t tow . otherwise that command is not accepted and erasure does not start. it is recommended that processor interrupts be disabled during this time to guarantee such condition. the interrupts can reoccur after the last sector erase command is written. a time-out of t tow from the rising edge of last ce or we , whichever starts first, initiates the execution of the sector erase command (s) . if another falling edge of ce or we , whichever starts first occurs within the t tow time-out window, the timer is reset (monitor dq 3 to determine if the sector erase timer window is still open, see section dq 3 , sector erase timer) . resetting the device once execution begins may corrupt the data in the sector. in that case restart the erase on those sectors and allow them to complete. refer to write operation status section for sector erase timer operation. loading the sector erase buffer may be done in any sequence and with any number of sectors (0 to 141) . sector erase does not require the user to program the device before erase. the device automatically programs all memory locations in the sector (s) to be erased prior to electrical erase (preprogram function) . when erasing a sector, the rest remain unaffected. the system is not required to provide any controls or timings during these operations. the system can determine the status of the erase operation by using dq 7 (data polling) , dq 6 (toggle bit) or ry/by . the sector erase begins after the t tow time-out from the rising edge of ce or we , whichever starts first, for the last sector erase command pulse and terminates when the data on dq 7 is 1 (see write operation status section) at which the device returns to the read mode. data polling and toggle bit must be performed at an address within any of the sectors being erased. multiple sector erase time = [sector erase time + sector program time (preprogramming) ] number of sector erase in case of multiple sector erase across bank boundaries, a read from the bank (read-while-erase) to which sectors being erased belong cannot be performed. (2) embedded erase tm algorithm in n flow chart illustrates the typical command strings and bus operations.
mbm29dl64df -70 31 erase suspend/resume the erase suspend command allows the user to interrupt sector erase operation and then reads data from or programs to a sector not being erased. this command is applicable only during the sector erase operation which includes the time-out period for sector erase. writing the erase suspend command (b0h) during the sector erase time-out results in immediate termination of the time-out period and suspension of the erase operation. writing the erase resume command (30h) resumes the erase operation. the bank address of sector being erased or erase-suspended should be set when writing the erase suspend or erase resume command. when the erase suspend command is written during the sector erase operation, the device takes a maximum of t spd to suspend the erase operation. when the device enters the erase-suspended mode, the ry/by output pin is at high-z and the dq 7 is at logic 1, and dq 6 stops toggling. the user must use the address of the erasing sector for reading dq 6 and dq 7 to determine if the erase operation is suspended. further writes of the erase suspend command are ignored. when the erase operation is suspended, the device defaults to the erase-suspend-read mode. reading data in this mode is the same as reading from the standard read mode, except that the data must be read from sectors that have not been erase-suspended. reading successively from the erase-suspended sector while the device is in the erase-suspend-read mode may cause dq 2 to toggle (see the section on dq 2 ) . after entering the erase-suspend-read mode, the user can program the device by writing the appropriate com- mand sequence for program. this program mode is known as the erase-suspend-program mode. again it is the same with programming in the regular program mode, except that the data must be programmed to sectors not being erase-suspended. reading successively from the erase-suspended sector while the device is in the erase- suspend-program mode may cause dq 2 to toggle. the end of the erase-suspended program operation is detected by the ry/by output pin, data polling of dq 7 or by the toggle bit i (dq 6 ) , which is the same with the regular program operation. note that dq 7 must be read from the program address while dq 6 can be read from any address within bank being erase-suspended. to resume the operation of sector erase, the resume command (30h) should be written to the bank being erase suspended. any further writes of the resume command at this point are ignored. another erase suspend command can be written after the chip resumes erasing. fast mode set/reset fast mode function dispenses with the initial two unclock cycles required in the standard program command sequence by writing the fast mode command into the command register. in this mode the required bus cycle for programming consists of two bus cycles instead of four in standard program command. do not write erase command in this mode. the read operation is also executed after exiting from the fast mode. to exit from this mode, write fast mode reset command into the command register. the first cycle must contain the bank address. the v cc active current is required even if ce = v ih during fast mode. fast programming during fast mode, programming is executed with two bus cycle operation. the embedded program algorithm is executed by writing program set-up command (a0h) and data write cycles (pa/pd) . see (8) embedded programming algorithm for fast mode in n flow chart. the address of the program set-up command is dont care. fast program command, with the exception of its process taken place at the two bus cycles, emulates the conventional programming so that the programming termination can be detected by data polling of dq 7 , toggle bit i (dq 6 ) and ry/by output pins. extended sector group protection in addition to normal sector group protection, the device has extended sector group protection as extended function. this function enables protection of the sector group by forcing v id on reset pin and writes a command sequence. unlike conventional procedures, it is not necessary to force v id and control timing for control pins. the extended sector group protection requires v id on reset pin only. with this condition the operation is initiated by writing the set-up command (60h) in the command register. then the sector group addresses pins (a 21 , a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 and a 12 ) and (a 6 , a 3 , a 2 , a 1 , a 0 ) = (0, 0, 0, 1, 0) should be set to the sector group to be protected (setting v il for the other addresses pins is recommended) , and an extended sector group
mbm29dl64df -70 32 protection command (60h) should be written. a sector group is typically protected in 250 m s. to verify program- ming of the protection circuitry, the sector group addresses pins (a 21 , a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 and a 12 ) and (a 6 , a 3 , a 2 , a 1 , a 0 ) = (0, 0, 0, 1, 0) should be set a command (40h) should be written. following the command write, a logic 1 at device output dq 0 will produce a protected sector in the read operation. if the output is logic 0, write the extended sector group protection command (60h) again. to terminate the operation, it is necessary to set reset pin to v ih . (refer to (17) extended sector group protection timing diagram in n timing diagram and (7) extended sector group protection algorithm in n flow chart.) query (cfi : common flash memory interface) the cfi (common flash memory interface) specification outlines device and the host system software interro- gation handshake, which allows specific vendor-specified software algorithms to be used for entire families of devices. this allows device-independent, jedec id-independent and forward-and backward-compatible soft- ware support for the specified flash device families. refer to common flash memory interface code in detail. the operation is initiated by writing the query command (98h) into the command register. the bank address should be set when writing this command. then the device information can be read from the bank, and data from the memory cell can be read from the another bank. the higher order address (a 21 , a 20 , a 19 ) required for reading out the cfi codes demands that the bank address (ba) be set at the write cycle. following the command write, a read cycle from specific address retrieves device information. note that output data of upper byte (dq 15 to dq 8 ) is 0 in word mode (16 bit) read. refer to common flash memory interface code. to terminate operation, write the read/reset command sequence into the register. hiddenrom region the hiddenrom feature provides flash memory region that the system may access through a new command sequence. this is primarily intended for customers who wish to use an electronic serial number (esn) in the device with the esn protected against modification. once the hiddenrom region is protected, any further modification of that region becomes impossible. this ensures the security of the esn once the product is shipped to be sold. the hiddenrom region is 256 bytes in length and is stored at the same address of sa0 in bank a. the device occupies the address of the byte mode 000000h to 0000ffh (word mode 000000h to 00007fh) . after the system writes the enter hiddenrom command sequence, the system reads the hiddenrom region by using the addresses normally occupied by the boot sector (particular area of sa0) . that is, the device sends all commands that would normally be sent to the boot sector (particular area of sa0) to the hiddenrom region. this mode of operation continues until the system issues the exit hiddenrom command sequence, or until power is removed from the device. on power-up, or following a hardware reset, the device reverts to sending commands to the boot sector. when reading the hiddenrom region, either change addresses or change ce pin from h to l. the same procedure should be taken (changing addresses or ce pin from h to l) after the system issues the exit hiddenrom command sequence to read actual memory cell data. hiddenrom entry command the device has a hiddenrom area with one time protect function. this area is to enter the security code and to remain once set. programming is allowed in this area until it is protected. however once protection goes on, unprotecting it is not allowed. therefore extreme caution is required. the hiddenrom area is 256 bytes. this area is normally the outermost 8 kbyte boot block area in bank a. therefore write the hiddenrom entry command sequence to enter the hiddenrom area. it is called hiddenrom mode when the hiddenrom area appears. sectors other than the boot block area sa0 can be read during hiddenrom mode. read/program of the hiddenrom area is possible during hiddenrom mode. write the hiddenrom reset command sequence to exit the hiddenrom mode. the bank address of the hiddenrom should be set on the third cycle of this reset command sequence. in hiddenrom mode, the simultaneous operation cannot be executed multi-function mode between the hid- denrom area and the bank a.
mbm29dl64df -70 33 hiddenrom program command to program the data to the hiddenrom area, write the hiddenrom program command sequence during hid- denrom mode. this command is the same with the usual program command, except that it needs to write the command during hiddenrom mode. therefore the detection of completion method is the same, using the dq 7 data polling, dq 6 toggle bit and ry/by pin. you should pay attention to the address to be programmed. if an address not in the hiddenrom area is selected, the previous data is deleted. hiddenrom protect command there are two methods to protect the hiddenrom area. one of them is to write the sector group protect setup command (60h) , set the sector address in the hiddenrom area and (a 6 , a 3 , a 2 , a 1 , a 0 ) = (0, 0, 0, 1, 0) , and write the sector group protect command (60h) during the hiddenrom mode. the same command sequence is used because it is the same with the extension sector group protect, except that it is in the hiddenrom mode and does not apply high voltage to the reset pin. refer to extended sector group protection for details of extension sector group protect setting. the other method is to apply high voltage (v id ) to a 9 and oe , set the sector address in the hiddenrom area and (a 6 , a 3 , a 2 , a 1 , a 0 ) = (0, 0, 0, 1, 0) , and apply the write pulse during the hiddenrom mode. to verify the protect circuit, apply high voltage (v id ) to a 9 , specify (a 6 , a 3 , a 2 , a 1 , a 0 ) = (0, 0, 0, 1, 0) and the sector address in the hiddenrom area, and read. when 1 appears on dq 0 , the protect setting is completed. 0 will appear on dq 0 if it is not protected. apply write pulse again. the same command sequence is used for the above method because other than the hiddenrom mode, it is the same method with the sector group protect previously mentioned. refer to secor group protection for details of the sector group protect setting. take note that other sector groups are affected if an address other than those for the hiddenrom area is selected for the sector group address. pay close attention that once it is protected, protection cannot be cancelled. write operation status details in hardware sequence flags are all the status flags which determine the status of the bank for the current mode operation. the read operation from the bank which does not operate embedded algorithm returns data of memory cells. these bits offer a method for determining whether an embedded algorithm is properly completed. the information on dq 2 is address-sensitive. this means that if an address from an erasing sector is consecutively read, the dq 2 bit will toggle. however, dq 2 will not toggle if an address from a non-erasing sector is consecutively read. this allows users to determine which sectors are in erase. the status flag is not output from banks (non-busy banks) that do not execute embedded algorithms. for example a bank (busy bank) is executing an embedded algorithm. when the read sequence is [1] < busy bank > , [2] < non-busy bank > , [3] < busy bank > , the dq 6 toggles in the case of [1] and [3]. in case of [2], the data of memory cells are output. in the erase-suspend read mode with the same read sequence, dq 6 will not be toggled in [1] and [3]. in the erase suspend read mode, dq 2 is toggled in [1] and [3]. in case of [2], the data of memory cell is output.
mbm29dl64df -70 34 hardware sequence flags table *1 : successive reads from the erasing or erase-suspend sector causes dq 2 to toggle. *2 : reading from non-erase suspend sector address indicates logic 1 at the dq 2 bit. dq 7 data polling the device features data polling as a method to indicate the host that the embedded algorithms are in progress or completed. during the embedded program algorithm, an attempt to read the device produces reverse data last written to dq 7 . upon completion of the embedded program algorithm, an attempt to read the device produces true data last written to dq 7 . during the embedded erase algorithm, an attempt to read the device produces a 0 at the dq 7 output. upon completion of the embedded erase algorithm, an attempt to read device produces a 1 on dq 7 . the flowchart for data polling (dq 7 ) is shown in (3) data polling algorithm in n flow chart. for programming, the data polling is valid after the rising edge of the fourth write pulse in the four write pulse sequences. for chip erase and sector erase, the data polling is valid after the rising edge of the sixth write pulse in the six write pulse sequences. data polling also works as a flag to indicate whether the device is in erase-suspend mode. dq 7 goes from 0 to 1 during erase-suspend mode. notice that to determine dq 7 entering erase- suspend mode, indicate the sector address of sector being erased. data polling must be performed at sector addresses of sectors being erased, not protected sectors. otherwise the status may become invalid. if a program address falls within a protected sector, data polling on dq 7 is active for approximately 1 m s, then that bank returns to the read mode. after an erase command sequence is written, if all sectors selected for erasing are protected, data polling on dq 7 is active for approximately 400 m s, then the bank returns to read mode. once the embedded algorithm operation is close to being completed, the device data pins (dq 7 ) may change asynchronously while the output enable (oe ) is asserted low. this means that device is driving status information on dq 7 at one instant, and then that bytes valid data the next. depending on when the system samples the dq 7 output, it may read the status or valid data. even if device completes the embedded algorithm operation and dq 7 has valid data, data outputs on dq 6 to dq 0 may still be invalid. the valid data on dq 7 to dq 0 is read on successive read attempts. status dq 7 dq 6 dq 5 dq 3 dq 2 in progress embedded program algorithm dq 7 toggle 0 0 1 embedded erase algorithm 0 toggle 0 1 toggle * 1 erase suspended mode erase suspend read (erase suspended sector) 1 1 0 0 toggle erase suspend read (non-erase suspended sector) data data data data data erase suspend program (non-erase suspended sector) dq 7 toggle 0 0 1 * 2 program suspended mode program suspend read (program suspended sector) data data data data data program suspend read (non-program suspended sector) data data data data data exceeded time limits embedded program algorithm dq 7 toggle 1 0 1 embedded erase algorithm 0 toggle 1 1 n/a erase suspended mode erase suspend program (non-erase suspended sector) dq 7 toggle 1 0 n/a
mbm29dl64df -70 35 the data polling feature is only active during the embedded programming algorithm, embedded erase algo- rithm, erase suspend mode or sector erase time-out. see data polling timing specifications and diagrams. dq 6 toggle bit i the device also features the toggle bit i as a method to indicate to the host system that the embedded algorithms are in progress or completed. during embedded program or erase algorithm cycle, successive attempts to read (ce or oe toggling) data from the busy bank results in dq 6 toggling between one and zero. once the embedded program or erase algorithm cycle is completed, dq 6 stops toggling and valid data is read on the next successive attempts. during programming, the toggle bit i is valid after the rising edge of the fourth write pulse in the four write pulse sequences. for chip erase and sector erase, the toggle bit i is valid after the rising edge of the sixth write pulse in the six write pulse sequences. the toggle bit i is active during the sector time out. in program operation, if the sector being written to is protected, the toggle bit toggles for about 1 m s and then stops toggling with data unchanged. in erase operation, the device erases all selected sectors except for pro- tected ones. if all selected sectors are protected, the chip toggles the toggle bit for about 400 s and then drop back into read mode, having data kept remained. either ce or oe toggling causes dq 6 to toggle. dq 6 determines whether a sector erase is active or is erase-suspended. when a bank is actively erased (that is, the embedded erase algorithm is in progress) , dq 6 toggles. when a bank enters the erase suspend mode, dq 6 stops toggling. successive read cycles during erase-suspend-program cause dq 6 to toggle. to operate toggle bit function properly, ce or oe must be high when bank address is changed. see (7) ac waveforms for toggle bit i during embedded algorithm operations (in n timing diagram) in for the toggle bit i timing specifications and diagrams. dq 5 exceeded timing limits dq 5 indicates if the program or erase time exceeds the specified limits (internal pulse count) . under these conditions dq 5 produces 1. this is a failure condition indicating that the program or erase cycle was not successfully completed. data polling is only operating function of the device under this condition. the ce circuit partially powers down device under these conditions (to approximately 2 ma) . the oe and we pins control the output disable functions as described in user bus operations. the dq 5 failure condition may also appear if the user tries to program a non-blank location without pre-erase. in this case the device locks out and never completes the embedded algorithm operation. hence the system never reads valid data on dq 7 bit and dq 6 never stop toggling. once the device exceeds timing limits, the dq 5 bit indicates a 1. please note that this is not a device failure condition since the device was incorrectly used. if this occurs, reset device with the command sequence. dq 3 sector erase timer after completion of the initial sector erase command sequence, sector erase time-out begins. dq 3 remains low until the time-out is completed. data polling and toggle bit are valid after the initial sector erase command sequence. if data polling or the toggle bit i indicates that a valid erase command is written, dq 3 determines whether the sector erase timer window is still open. if dq 3 is high (1) the internally controlled erase cycle begins. if dq 3 is low (0) , the device accepts additional sector erase commands. to insure the command is accepted, the system software checks the status of dq 3 prior to and following each subsequent sector erase command. if dq 3 is high on the second status check, the command may not be accepted. see hardware sequence flags.
mbm29dl64df -70 36 dq 2 toggle bit ii this toggle bit ii, along with dq 6 , determines whether the device is in the embedded erase algorithm or in erase suspend. successive reads from the erasing sector causes dq 2 to toggle during the embedded erase algorithm. if the device is in the erase-suspended-read mode, successive reads from the erase-suspended sector causes dq 2 to toggle. when the device is in the erase-suspended-program mode, successive reads from the non-erase suspended sector indicates a logic 1 at the dq 2 bit. dq 6 is different from dq 2 in that dq 6 toggles only when the standard program or erase, or erase suspend program operation is in progress. these two status bits, along with that of dq 7 , operate as follows : for example dq 2 and dq 6 determine if the erase-suspend-read mode is in progress. (dq 2 toggles while dq 6 does not.) see also toggle bit status table and dq 2 vs.dq 6 waveform. furthermore dq 2 determines which sector is being erased. at the erase mode, dq 2 toggles if this bit is read from an erasing sector. to operate toggle bit function properly, ce or oe must be high when bank address is changed. reading toggle bits dq 6 /dq 2 whenever the system initially begins reading toggle bit status, it must read dq 7 to dq 0 at least twice in a row to determine whether a toggle bit is on. typically the system would note and store the value of the toggle bit after the first read. after the second read, the system compares the new value of the toggle bit with the first. if the toggle bit is not toggling, this indicates that the device completes the program or erase operation. the system reads array data on dq 7 to dq 0 on the following read cycle. however if after the initial two read cycles, the system determines that the toggle bit is still on, the system also should note whether the value of dq 5 is high (see the section on dq 5 ) . if it is, the system should then determine again whether the toggle bit is toggling, since the toggle bit may have stopped toggling just as dq 5 went high. if the toggle bit is no longer toggling, the device successfully completes the program or erase operation. if it is still toggling, the device does not complete the operation successfully, and the system must write the reset command to return to reading array data. the remaining scenario is that the system initially determines that the toggle bit is toggling and dq 5 has not gone high. the system continues to monitor the toggle bit and dq 5 through successive read cycles, determining the status as described in the previous paragraph. alternatively the system chooses to perform other system tasks. in this case the system must start at the beginning of the algorithm to determine the status of the operation. toggle bit status table *1 : successive reads from the erasing or erase-suspend sector cause dq 2 to toggle. *2 : reading from the non-erase suspend sector address indicates logic 1 at the dq 2 bit. ry/by ready/busy the device provides a ry/by open-drain output pin as a way to indicate that embedded algorithms are either in progress or have been completed. when output is low the device is busy with either a program or erase mode dq 7 dq 6 dq 2 program dq 7 toggle 1 erase 0 toggle toggle* 1 erase-suspend read (erase-suspended sector) 11toggle erase-suspend program dq 7 toggle 1* 2
mbm29dl64df -70 37 operation. if output is high, the device is ready to accept any read/write or erase operation. if the device is placed in an erase suspend mode, ry/by output is high. during programming, the ry/by pin is driven low after the rising edge of the fourth write pulse. during an erase operation, the ry/by pin is driven low after the rising edge of the sixth write pulse. ry/by pin indicates busy condition during reset pulse. refer to (10) ry/by timing diagram during program/erase operation timing diagram and (11) reset , ry/by timing diagram in n timing diagram. ry/by pin is pulled high in standby mode. since this is an open-drain output, pull-up resistor needs to be connected to v cc ; multiples of devices may be connected to the host system via more than one ry/by pin in parallel. data protection the device offers protection against accidental erasure or programming caused by spurious system level signals that may exist during power transitions. during power-up the device automatically resets the internal state machine in read mode. with its control register architecture, alteration of memory contents only occurs after successful completion of specific multi-bus cycle command sequences. the device also incorporates several features to prevent inadvertent write cycles resulting from v cc power-up and power-down transitions or system noise. low v cc write inhibit to avoid initiation of a write cycle during v cc power-up and power-down, the write cycle is locked out for v cc less than v lko . if v cc < v lko , the command register is disabled and all internal program/erase circuits are disabled. under this condition the device resets to the read mode. subsequent writes are ignored until the v cc level goes higher than v lko . it is the users responsibility to ensure that the control pins are logically correct to prevent unintentional writes when v cc is above v lko . if the embedded erase algorithm is interrupted, the intervened erasing sector (s) is (are) not valid. write pulse glitch protection noise pulses of less than 3 ns (typical) on oe , ce or w e does not initiate write cycle. logical inhibit writing is prohibited by holding any one of oe = v il , ce = v ih or we = v ih . to initiate a write cycle ce and we must be logical zero while oe is a logical one. power-up write inhibit power-up of the device with we = ce = v il and oe = v ih does not accept commands on the rising edge of we . internal state machine is automatically reset to the read mode on power-up. sector group protection device user is able to protect each sector group individually to store and protect data. protection circuit voids both program and erase command that are addressed to protect sectors. any commands to program or erase addressed to protected sector are ignored (see n functional description, sector group protection) .
mbm29dl64df -70 38 n absolute maximum ratings *1: voltage is defined on the basis of v ss = gnd = 0 v. *2: minimum dc voltage on input or i/o pins is - 0.5 v. during voltage transitions, input or i/o pins may undershoot v ss to - 2.0 v for periods of up to 20 ns. maximum dc voltage on input or i/o pins is v cc + 0.5 v. during voltage transitions, input or i/o pins may overshoot to v cc + 2.0 v for periods of up to 20 ns. *3: minimum dc input voltage on a 9 , oe and reset pins is - 0.5 v. during voltage transitions, a 9 , oe and reset pins may undershoot v ss to - 2.0 v for periods of up to 20 ns. voltage difference between input and supply voltage (v in - v cc ) does not exceed + 9.0 v. maximum dc input voltage on a 9 , oe and reset pins is + 13.0 v which may overshoot to + 14.0 v for periods of up to 20 ns. *4: minimum dc input voltage on wp /acc pin is - 0.5 v. during voltage transitions, wp /acc pin may undershoot v ss to - 2.0 v for periods of up to 20 ns. maximum dc input voltage on w p /acc pin is + 10.5 v which may overshoot to + 12.0 v for periods of up to 20 ns when vcc is applied. warning: semiconductor devices can be permanently damaged by application of stress (voltage, current, temperature, etc.) in excess of absolute maximum ratings. do not exceed these ratings. n recommended operating conditions * : voltage is defined on the basis of v ss = gnd = 0 v. note: operating ranges define those limits between which the proper device function is guaranteed. warning: the recommended operating conditions are required in order to ensure the normal operation of the semiconductor device. all of the devices electrical characteristics are warranted when the device is operated within these ranges. always use semiconductor devices within their recommended operating condition ranges. operation outside these ranges may adversely affect reliability and could result in device failure. no warranty is made with respect to uses, operating conditions, or combinations not represented on the data sheet. users considering application outside the listed conditions are advised to contact their fujitsu representatives beforehand. parameter symbol rating unit min max storage temperature tstg - 55 + 125 c ambient temperature with power applied t a - 40 + 85 c voltage with respect to ground all pins except a 9 , oe , and reset * 1, * 2 v in , v out - 0.5 v cc + 0.5 v power supply voltage * 1 v cc - 0.5 + 4.0 v a 9 , oe , and reset * 1, * 3 v in - 0.5 + 13.0 v wp /acc * 1, * 4 v acc - 0.5 + 10.5 v parameter symbol value unit min max ambient temperature t a - 40 + 85 c power supply voltage* v cc + 2.7 + 3.6 v
mbm29dl64df -70 39 n maximum overshoot/maximum undershoot + 0.6 v - 0.5 v 20 ns - 2.0 v 20 ns 20 ns maximum undershoot waveform v cc + 0.5 v + 2.0 v v cc + 2.0 v 20 ns 20 ns 20 ns maximum overshoot waveform 1 + 13.0 v v cc + 0.5 v + 14.0 v 20 ns 20 ns 20 ns maximum overshoot waveform 2 note : applicable for a 9 , oe and reset .
mbm29dl64df -70 40 n dc characteristics *1 : i cc current listed includes both the dc operating current and the frequency dependent component. *2 : i cc active while embedded algorithm (program or erase) is in progress. *3 : this timing is only for sector group protection operation and autoselect mode. *4 : applicable for only v cc . *5 : automatic sleep mode enables the low power mode when addresses remain stable for 150 ns. *6 : embedded algorithm (program or erase) is in progress (@5 mhz.) parameter sym- bol conditions value unit min typ max input leakage current i li v in = v ss to v cc , v cc = v cc max - 1.0 ?+ 1.0 m a output leakage current i lo v out = v ss to v cc , v cc = v cc max - 1.0 ?+ 1.0 m a a 9 , oe , reset inputs leakage current i lit v cc = v cc max, a 9 , oe , reset = 12.5 v ??+ 35 m a wp /acc accelerated program current i lia v cc = v cc max, wp /acc = v acc max ?? 20 ma v cc active current * 1 i cc1 ce = v il , oe = v ih , f = 5 mhz byte ?? 16 ma word ?? 18 ce = v il , oe = v ih , f = 1 mhz byte ?? 4 ma word ?? 4 v cc active current * 2 i cc2 ce = v il , oe = v ih ?? 30 ma v cc current (standby) i cc3 v cc = v cc max, ce = v cc 0.3 v, reset = v cc 0.3 v, wp /acc = v cc 0.3 v ? 15 m a v cc current (standby, reset) i cc4 v cc = v cc max, reset = v ss 0.3 v ? 15 m a v cc current (automatic sleep mode) * 5 i cc5 v cc = v cc max, ce = v ss 0.3 v, reset = v cc 0.3 v v in = v cc 0.3 v or v ss 0.3 v ? 15 m a v cc active current * 6 (read-while-program) i cc6 ce = v il , oe = v ih byte ?? 46 ma word ?? 48 v cc active current * 6 (read-while-erase) i cc7 ce = v il , oe = v ih byte ?? 46 ma word ?? 48 v cc active current (erase-suspend-program) i cc8 ce = v il , oe = v ih ?? 40 ma input low level v il ?- 0.5 ? 0.6 v input high level v ih ? 2.0 ? v cc + 0.3 v voltage for autoselect and sector protection (a 9 , oe , reset ) * 3, * 4 v id ? 11.5 12 12.5 v voltage for wp /acc sector protection/unprotection and program acceleration * 4 v acc ? 8.5 9.0 9.5 v output low voltage level v ol i ol = 4 ma, v cc = v cc min ?? 0.45 v output high voltage level v oh1 i oh = - 2.0 ma, v cc = v cc min 2.4 ?? v v oh2 i oh = - 100 m av cc - 0.4 ?? v low v cc lock-out voltage v lko ? 2.3 2.4 2.5 v
mbm29dl64df -70 41 n ac characteristics ? read only operations characteristics note : test conditions : output load : 30 pf (mbm29dl64df -70 ) input rise and fall times : 5 ns input pulse levels : 0.0 v or v cc timing measurement reference level input : 0.5 v cc output : 0.5 v cc parameter symbol condition value (note) unit jedec standard min max read cycle time t avav t rc ? 70 ? ns address to output delay t avqv t acc ce = v il oe = v il ? 70 ns chip enable to output delay t elqv t ce oe = v il ? 70 ns output enable to output delay t glqv t oe ?? 30 ns chip enable to output high-z t ehqz t df ?? 25 ns output enable to output high-z t ghqz t df ?? 25 ns output hold time from addresses, ce or oe , whichever occurs first t axqx t oh ? 0 ? ns reset pin low to read mode ? t ready ?? 20 m s ce to byte switching low or high ? t elfl t elfh ?? 5ns c l 3.3 v diodes = 1 n3064 or equivalent 2.7 k w device under test 1 n3064 or equivalent 6.2 k w test conditions notes: c l = 30 pf including jig capacitance (MBM29DL64DF-70) in case of c l = 100 pf, the device can be operated at an access time of 80 ns.
mbm29dl64df -70 42 ? write/erase/program operations (continued) parameter symbol value unit jedec standard min typ max write cycle time t avav t wc 70 ?? ns address setup time t avwl t as 0 ?? ns address setup time to oe low during toggle bit polling ? t aso 12 ?? ns address hold time t wlax t ah 30 ?? ns address hold time from ce or oe high during toggle bit polling ? t aht 0 ?? ns data setup time t dvwh t ds 25 ?? ns data hold time t whdx t dh 0 ?? ns output enable hold time read ? t oeh 0 ?? ns toggle and dat a polling 10 ?? ns ce high during toggle bit polling ? t ceph 20 ?? ns oe high during toggle bit polling ? t oeph 20 ?? ns read recover time before write t ghwl t ghwl 0 ?? ns read recover time before write t ghel t ghel 0 ?? ns ce setup time t elwl t cs 0 ?? ns we setup time t wlel t ws 0 ?? ns ce hold time t wheh t ch 0 ?? ns we hold time t ehwh t wh 0 ?? ns write pulse width t wlwh t wp 35 ?? ns ce pulse width t eleh t cp 35 ?? ns write pulse width high t whwl t wph 20 ?? ns ce pulse width high t ehel t cph 20 ?? ns programming operation byte t whwh1 t whwh1 ? 4 ?m s word ? 6 ?m s sector erase operation * 1 t whwh2 t whwh2 ? 0.5 ? s v cc setup time ? t vcs 50 ??m s rise time to v id * 2 ? t vidr 500 ?? ns rise time to v acc * 3 ? t vaccr 500 ?? ns voltage transition time * 2 ? t vlht 4 ??m s write pulse width * 2 ? t wpp 100 ??m s
mbm29dl64df -70 43 (continued) *1 : does not include preprogramming time. *2 : for sector group protection operation. *3 : for accelerated program operation only. parameter symbol value unit jedec standard min typ max oe setup time to we active * 2 ? t oesp 4 ??m s ce setup time to we active * 2 ? t csp 4 ??m s recover time from ry/by ? t rb 0 ?? ns reset pulse width ? t rp 500 ?? ns reset high level period before read ? t rh 200 ?? ns byte switching low to output high-z ? t flqz ?? 25 ns byte switching high to output active ? t fhqv ?? 70 ns program/erase valid to ry/by delay ? t busy ?? 90 ns delay time from embedded output enable ? t eoe ?? 70 ns erase time-out time ? t tow 50 ??m s erase suspend transition time ? t spd ?? 20 m s
mbm29dl64df -70 44 n erase and programming performance notes : typical erase conditions t a = + 25 c, v cc = 2.9 v typical program conditions t a = + 25 c, v cc = 2.9 v, data = checker n tsop (1) pin capacitance notes : test conditions t a = + 25 c, f = 1.0 mhz dq 15 /a -1 pin capacitance is stipulated by output capacitance. n fbga pin capacitance notes : test conditions t a = + 25 c, f = 1.0 mhz dq 15 /a -1 pin capacitance is stipulated by output capacitance. parameter limits unit comments min typ max sector erase time ? 0.5 2.0 s excludes programming time prior to erasure word programming time ? 6.0 100 m s excludes system-level overhead byte programming time ? 4.0 80 m s chip programming time ?? 200 s excludes system-level overhead program/erase cycle 100,000 ?? cycle ? parameter symbol condition value unit typ max input capacitance c in v in = 0 6.0 10.0 pf output capacitance c out v out = 0 8.5 12.0 pf control pin capacitance c in2 v in = 0 8.0 11.0 pf wp /acc pin capacitance c in3 v in = 0 9.0 12.0 pf parameter symbol condition value unit typ max input capacitance c in v in = 0 6.0 10.0 pf output capacitance c out v out = 0 8.5 12.0 pf control pin capacitance c in2 v in = 0 8.0 11.0 pf wp /acc pin capacitance c in3 v in = 0 9.0 12.0 pf
mbm29dl64df -70 45 n timing diagram ? key to switching waveforms (1) read operation timing diagram waveform inputs outputs must be steady may change from h to l may change from l to h "h" or "l": any change permitted does not apply will be steady will change from h to l will change from l to h changing, state unknown center line is high- impedance "off" state address address stable high-z high-z ce oe we outputs outputs valid t rc t acc t oe t df t ce t oh t oeh
mbm29dl64df -70 46 (2) hardware reset/read operation timing diagram (3) alternate we controlled program operation timing diagram address ce reset outputs high-z outputs valid address stable t rc t acc t rh t rp t rh t ce t oh address data ce oe we 3rd bus cycle data polling 555h pa a0h pd dq 7 d out d out pa t wc t as t ah t rc t ce t whwh1 t wph t wp t ghwl t ds t dh t df t oh t oe t cs t ch notes: pa is address of the memory location to be programmed. pd is data to be programmed at word address. dq 7 is the output of the complement of the data written to the device. d out is the output of the data written to the device. figure indicates the last two bus cycles out of four bus cycle sequence. these waveforms are for the 16 mode.
mbm29dl64df -70 47 (4) alternate ce controlled program operation timing diagram address data we oe ce 3rd bus cycle data polling 555h pa a0h pd dq 7 d out pa t wc t as t ah t whwh1 t cph t cp t ghel t ds t dh t ws t wh notes: pa is address of the memory location to be programmed. pd is data to be programmed at word address. dq 7 is the output of the complement of the data written to the device. d out is the output of the data written to the device. figure indicates the last two bus cycles out of four bus cycle sequence. these waveforms are for the 16 mode.
mbm29dl64df -70 48 (5) chip/sector erase operation timing diagram (6) data polling during embedded algorithm operation timing diagram address data v cc ce oe we 555h 2aah 555h 555h 2aah sa* t wc t as t ah t cs t ghwl t ch t wp t ds t vcs t dh t wph aah 55h 80h aah 55h 10h/ 30h 10h for chip erase * : sa is the sector address for sector erase. addresses = 555h (word) for chip erase. note : these waveforms are for the 16 mode. the addresses differ from the 8 mode. t oeh t ch t oe t ce t df t busy t eoe t whwh1 or 2 ce dq 7 dq 6 to dq 0 ry/by dq 7 dq 7 = valid data dq 6 to dq 0 = output flag dq 6 to dq 0 valid data oe we high-z high-z data data * * : dq 7 = valid data (the device has completed the embedded operation) .
mbm29dl64df -70 49 (7) ac waveforms for toggle bit i during embedded algorithm operations t aht ce address we ry/by oe dq 6 /dq 2 t dh t aso t oeph t aht t as t ceph t oe t ce t busy t oeh t oeh data toggle data toggle data toggle data stop toggling output valid * * : dq 6 stops toggling (the device has completed the embedded operation) .
mbm29dl64df -70 50 (8) bank-to-bank read/write timing diagram (9) dq 2 vs. dq 6 ce dq we address ba1 ba1 ba1 ba2 (555h) ba2 (pa) ba2 (pa) oe valid output valid output valid output status valid intput valid intput t rc t rc t rc t rc t wc t wc t aht t as t as t ah t acc t ce t oe t oeh t wp t ghwl t ds t df t dh t df t ceph read command command read read read (a0h) (pd) note : this is example of read for bank 1 and embedded algorithm (program) for bank 2. ba1 : address corresponding to bank 1 ba2 : address corresponding to bank 2 enter embedded erasing erase suspend erase resume enter erase suspend program erase suspend program erase complete erase erase suspend read erase suspend read erase dq 6 dq 2 * we toggle dq 2 and dq 6 with oe or ce * : dq 2 is read from the erase-suspended sector.
mbm29dl64df -70 51 (10) ry/by timing diagram during program/erase operation timing diagram (11) reset , ry/by timing diagram (12) timing diagram for word mode configuration ce ry/by we rising edge of the last we signal t busy entire programming or erase operations t rp t rb t ready ry/by we reset t ce t fhqv t elfh a -1 data output (dq 7 to dq 0 ) data output (dq 14 to dq 0 ) dq 15 ce byte dq 14 to dq 0 dq 15 /a -1
mbm29dl64df -70 52 (13) timing diagram for byte mode configuration (14) byte timing diagram for write operations t elfl t acc t flqz a -1 data output (dq 14 to dq 0 ) data output (dq 7 to dq 0 ) dq 15 ce byte dq 14 to dq 0 dq 15 /a -1 t as t ah ce or we byte input valid falling edge of the last write signal
mbm29dl64df -70 53 (15) sector group protection timing diagram t wpp t vlht t vlht t oe t csp t oesp t vcs t vlht t vlht a 21 , a 20 , a 19 a 18 , a 17 , a 16 a 15 , a 14 , a 13 a 12 a 6 , a 3 , a 2 , a 0 a 1 a 9 v cc oe v id v ih v id v ih we ce data spax 01h spay spax : sector group address to be protected spay : next sector group address to be protected note : a -1 is v il on byte mode.
mbm29dl64df -70 54 (16) temporary sector group unprotection timing diagram unprotection period t vlht t vlht t vcs t vlht t vidr program or erase command sequence v cc v id v ih we ry/by ce reset
mbm29dl64df -70 55 (17) extended sector group protection timing diagram v cc we oe ce reset t wc t wc t vlht t vidr t vcs time-out spax spax spay t wp t oe 60h 01h 40h 60h 60h data address a 6 , a 3 , a 2 , a 0 a 1 spax : sector group address to be protected spay : next sector group address to be protected time-out : time-out window = 250 m s (min)
mbm29dl64df -70 56 (18) accelerated program timing diagram v ih wp/acc v cc ce we ry/by t vlht program command sequence t vlht t vcs t vaccr v acc t vlht acceleration period
mbm29dl64df -70 57 n flow chart (1) embedded program tm algorithm 555h/aah 555h/a0h 2aah/55h program address/program data programming completed last address ? increment address verify data ? data polling program command sequence (address/command) : write program command sequence (see below) start no no yes yes embedded program algorithm in program note : the sequence is applied for 16 mode. embedded algorithm
mbm29dl64df -70 58 (2) embedded erase tm algorithm 555h/aah 555h/80h 2aah/55h 555h/aah 555h/10h 2aah/55h 555h/aah 555h/80h 2aah/55h 555h/aah sector address /30h sector address /30h sector address /30h 2aah/55h erasure completed data = ffh ? data polling write erase command sequence (see below) start no yes embedded erase algorithm in progress chip erase command sequence (address/command) : individual sector/multiple sector erase command sequence (address/command) : additional sector erase commands are optional. note : the sequence is applied for 16 mode. embedded algorithm
mbm29dl64df -70 59 (3) data polling algorithm dq 7 = data? dq 5 = 1? fail pass dq 7 = data? * read byte (dq 7 to dq 0 ) addr. = va read byte (dq 7 to dq 0 ) addr. = va start no no no yes yes yes * : dq 7 is rechecked even if dq 5 = 1 because dq 7 may change simultaneously with dq 5 . va = address for programming = any of the sector addresses within the sector being erased during sector erase or multiple sector erases operation. = any of the sector addresses within the sector not being protected during chip erase operation.
mbm29dl64df -70 60 (4) toggle bit algorithm dq 6 = toggle? dq 5 = 1? read dq 7 to dq 0 addr. = va read dq 7 to dq 0 addr. = va read dq 7 to dq 0 addr. = va start no no yes yes *1, *2 dq 6 = toggle? no yes program/erase operation not complete.write reset command program/erase operation complete read dq 7 to dq 0 addr. = va *1, *2 *1 *1 : read toggle bit twice to determine whether it is toggling. *2 : recheck toggle bit because it may stop toggling as dq 5 changes to 1. va = bank address being executed embedded algorithm.
mbm29dl64df -70 61 (5) sector group protection algorithm start no no no yes yes yes data = 01h? device failed plscnt = 25? plscnt = 1 remove v id from a 9 write reset command remove v id from a 9 write reset command sector group protection completed protect another sector group? increment plscnt read from sector group addr. = spa, a 1 = v ih a 6 = a 3 = a 2 = a 0 = v il setup sector group addr. a 21 , a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 , a 12 oe = v id , a 9 = v id ce = v il , reset = v ih a 6 = a 3 = a 2 = a 0 = v il , a 1 = v ih activate we pulse time out 100 m s we = v ih , ce = oe = v il (a 9 should remain v id ) () () * * : a -1 is v il in byte mode.
mbm29dl64df -70 62 (6) temporary sector group unprotection algorithm start perform erase or program operations reset = v id *1 reset = v ih temporary sector group unprotection completed *2 *1 : all protected sector groups are unprotected. *2 : all previously protected sector groups are reprotected.
mbm29dl64df -70 63 (7) extended sector group protection algorithm start no yes yes data = 01h? plscnt = 1 no no yes device failed plscnt = 25? remove v id from reset write reset command sector group protection completed protect other sector group? increment plscnt read from sector group address (addr. = spa, a 1 = v ih , a 6 = a 3 = a 2 = a 0 = v il ) remove v id from reset write reset command time out 250 m s reset = v id wait to 4 m s no yes setup next sector group address device is operating in temporary sector group unprotection mode to protect secter group write 60h to secter address (a 6 = a 3 = a 2 = a 0 = v il , a 1 = v ih ) to verify sector group protection write 40h to secter address (a 6 = a 3 = a 2 = a 0 = v il , a 1 = v ih ) to setup sector group protection write xxxh/60h extended sector group protection entry?
mbm29dl64df -70 64 (8) embedded programming algorithm for fast mode 555h/aah 555h/20h (ba) xxxh/90h xxxh/f0h xxxh/a0h 2aah/55h program address/program data programming completed last address? increment address verify data? data polling start no no yes yes set fast mode in fast program reset fast mode note : the sequence is applied for 16 mode. fast mode algorithm
mbm29dl64df -70 65 n ordering information mbm29dl64d f 70 tn package type tn = 48-pin thin small outline package (tsop) normal bend pbt = 48-ball fine pitch ball grid array package (fbga) speed option see product selector guide device revision device number/description mbm29dl64d 64 mega-bit (8 m 8-bit or 4 m 16-bit) flash memory 3.0 v-only read, program, and erase part no. package access time (ns) remarks mbm29dl64df70tn 48-pin plastic tsop (1) (fpt-48p-m19) normal bend 70 mbm29dl64df70pbt 48-pin plastic fbga (bga-48p-m13) 70
mbm29dl64df -70 66 n package dimensions (continued) 48-pin plastic tsop (1) (fpt-48p-m19) note 1) * : values do not include resin protrusion. resin protrusion and gate protrusion are + 0.15 (.006) max (each side) . note 2) pins width and pins thickness include plating thickness. note 3) pins width do not include tie bar cutting remainder. dimensions in mm (inches) note : the values in parentheses are reference values. C .003 +.001 C 0.08 +0.03 .007 0.17 "a" (stand off height) 0.10(.004) (mounting height) (.472 .008) 12.00 0.20 lead no. 48 25 24 1 (.004 .002) 0.10(.004) m 1.10 +0.10 C 0.05 +.004 C .002 .043 0.10 0.05 (.009 .002) 0.22 0.05 (.787 .008) 20.00 0.20 (.724 .008) 18.40 0.20 index 2003 fujitsu limited f48029s-c-6-7 c 0~8 ? 0.25(.010) 0.50(.020) 0.60 0.15 (.024 .006) details of "a" part * *
mbm29dl64df -70 67 (continued) 48-pin plastic fbga (bga-48p-m13) dimensions in mm (inches) note : the values in parentheses are reference values. c 2001 fujitsu limited b48013s-c-3-2 9.000.20(.354.008) 0.380.10(.015.004) (stand off) (mounting height) 8.000.20 (.315.008) 0.10(.004) 0.80(.031)typ 5.60(.220) 4.00(.157) 48-?0.450.10 (48-?.018.004) m ?0.08(.003) index h g fed c ba 6 5 4 3 2 1 c0.25(.010) .041 C.004 +.006 C0.10 +0.15 1.05
mbm29dl64df -70 fujitsu limited all rights reserved. the contents of this document are subject to change without notice. customers are advised to consult with fujitsu sales representatives before ordering. the information, such as descriptions of function and application circuit examples, in this document are presented solely for the purpose of reference to show examples of operations and uses of fujitsu semiconductor device; fujitsu does not warrant proper operation of the device with respect to use based on such information. when you develop equipment incorporating the device based on such information, you must assume any responsibility arising out of such use of the information. fujitsu assumes no liability for any damages whatsoever arising out of the use of the information. any information in this document, including descriptions of function and schematic diagrams, shall not be construed as license of the use or exercise of any intellectual property right, such as patent right or copyright, or any other right of fujitsu or any third party or does fujitsu warrant non-infringement of any third-partys intellectual property right or other right by using such information. fujitsu assumes no liability for any infringement of the intellectual property rights or other rights of third parties which would result from the use of information contained herein. the products described in this document are designed, developed and manufactured as contemplated for general use, including without limitation, ordinary industrial use, general office use, personal use, and household use, but are not designed, developed and manufactured as contemplated (1) for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could have a serious effect to the public, and could lead directly to death, personal injury, severe physical damage or other loss (i.e., nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system), or (2) for use requiring extremely high reliability (i.e., submersible repeater and artificial satellite). please note that fujitsu will not be liable against you and/or any third party for any claims or damages arising in connection with above-mentioned uses of the products. any semiconductor devices have an inherent chance of failure. you must protect against injury, damage or loss from such failures by incorporating safety design measures into your facility and equipment such as redundancy, fire protection, and prevention of over-current levels and other abnormal operating conditions. if any products described in this document represent goods or technologies subject to certain restrictions on export under the foreign exchange and foreign trade law of japan, the prior authorization by japanese government will be required for export of those products from japan. f0303 ? fujitsu limited printed in japan

▲Up To Search▲

Price & Availability of MBM29DL64DF-70

	To Download MBM29DL64DF-70 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .